How to configure, monitor, and withdraw from fee vaults on your OP Stack chain.
This guide covers the operational aspects of managing fee vaults on your OP Stack chain. For a conceptual overview of how fee vaults work, see Fee vaults.
Prerequisites
Access to the ProxyAdminOwner account (required for configuration changes)
Configuration changes require the ProxyAdminOwner account. If your chain uses a multisig as the ProxyAdminOwner, these calls must be executed through the multisig.
On CGT chains, fee vaults must withdraw to L2 (withdrawalNetwork = 1) with an L2 recipient. Deployment rejects L1 for CGT chains, but setWithdrawalNetwork does not: setting it to 0 after deployment makes nonzero withdraw() calls revert, because L2ToL1MessagePasser rejects native token value on CGT chains.
This withdraws the entire vault balance to the configured recipient.
Withdrawal behavior by network
L2 withdrawal (withdrawalNetwork = 1): Funds are transferred immediately to the recipient on L2. The transaction completes in a single step.
L1 withdrawal (withdrawalNetwork = 0): An L2-to-L1 withdrawal is initiated via the L2ToL1MessagePasser. After calling withdraw(), you must still:
Wait for the withdrawal to be included in an L2 output root
Prove the withdrawal on L1
Wait for the finalization period
Finalize the withdrawal on L1
For details on completing L1 withdrawals, see Withdrawal flow.
Initial configuration during deployment
Fee vault recipients, minimum withdrawal amounts, and withdrawal networks are configured during chain deployment with op-deployer. For details on setting these parameters, see the op-deployer setup guide.
Monitoring
It’s good practice to monitor your fee vaults regularly:
Vault balances: Track balances to know when withdrawals can be triggered.
totalProcessed: Monitor cumulative withdrawals over time to understand revenue trends.
Next steps
Read the fee vaults explainer to understand how vaults work at the protocol level.