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.
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.
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.