Process Meta Vaults

Prerequisites

• Operator installed: Follow the Installation → guide to set up the Operator Service
• Wallet ready: The operator needs a wallet to pay gas for transactions. See Wallet Setup → below.

Wallet Setup

Option A — Create a new wallet

Initialize a mnemonic with:

./operator init

Then create a wallet with:

./operator create-wallet

Option B — Use an existing wallet

Export a private key from an existing wallet, then set it as an environment variable:

export WALLET_PRIVATE_KEY="0xyour_private_key_here"

process-meta-vaults Command

The process-meta-vaults command triggers transactions to update states and process deposits and exits for one or more Meta Vaults.

Command Usage

./operator process-meta-vaults [OPTIONS]

Required Parameters

The following parameters are required:

• --vaults - Comma separated addresses of meta vaults to process
• --execution-endpoints - Comma separated API endpoints for execution nodes. You can find public RPC endpoints on Chainlist ↗
• If using Option A →: --wallet-file and --wallet-password-file flags
• If using Option B →: the WALLET_PRIVATE_KEY environment variable is picked up automatically

Optional Flags

Flag	Description
--network	The network: mainnet, hoodi, or gnosis
--graph-endpoint	API endpoint for graph node
--min-deposit-amount-gwei	Minimum amount in gwei that must accumulate in the vault to trigger deposits to the sub-vaults. Default: 10,000,000,000 Gwei (10 ETH/GNO)
--max-fee-per-gas-gwei	Maximum fee per gas for transactions. Default: 10 Gwei for Ethereum, 2 Gwei for Gnosis
-v, --verbose	Enable debug mode. Default: false

Example

./operator process-meta-vaults \
 --vaults=0x15639E82d2072Fa510E5d2b5F0db361c823bCad3 \
 --wallet-file=/Users/user/wallet.json \
 --wallet-password-file=/home/user/wallet-pass.txt \
 --execution-endpoints=https://execution-node

Example Output

Starting operator service, version v4.1.7
Started meta vault processing
Fetching meta vaults
Processing meta vault: 0x15639E82d2072Fa510E5d2b5F0db361c823bCad3
Getting state update calls for meta vault 0x34284C27A2304132aF751b0dEc5bBa2CF98eD039
Sub vault 0xba447498DC4c169f2b4f427B2c4D532320457E89 is not harvestable, skipping
No sub vault exit requests to claim for meta vault 0x34284C27A2304132aF751b0dEc5bBa2CF98eD039
Meta vault 0x34284C27A2304132aF751b0dEc5bBa2CF98eD039 state is up-to-date, no updates needed

Learn More

To learn more about what Meta Vaults are and how they work, see the Meta Vaults →