deploy_multichain_lagoon_vault

Documentation for eth_defi.lagoon.deployment.deploy_multichain_lagoon_vault function.

deploy_multichain_lagoon_vault(*, chain_web3, deployer, chain_configs, max_workers=None, lighter_activation=None)

Deploy Lagoon vaults across multiple chains with a shared deterministic Safe.

Uses CREATE2 via the canonical Safe v1.4.1 ProxyFactory to produce the same Safe address on every chain. Every chain gets a distinct Safe contract and guard module at matching addresses. Non-satellite chains additionally get a Lagoon vault paired with that chain’s Safe.

Deploys all chains in parallel using threads to minimise wall-clock time.

Each chain receives its own LagoonConfig with chain-specific whitelisting (ERC-4626 vaults, Hypercore vaults, CCTP, CowSwap, etc.) and an optional chain-specific Lagoon settlement safety policy. All configs must share the same safe_salt_nonce to ensure deterministic Safe addresses.

LagoonConfig.max_settlement_amount and its settlement window are forwarded to the public single-chain deployment API and is converted using that chain’s underlying token decimals. Configure it only for chains which deploy or reuse a Lagoon vault. Satellite chains contain only a Safe and guard module and therefore reject settlement-safety configuration instead of silently ignoring it.

Parameters

  • chain_web3 (dict[str, web3.main.Web3]) – Mapping of chain names (lowercase, matching eth_defi.chain.CHAIN_NAMES) to Web3 instances. Example: {"ethereum": w3_eth, "arbitrum": w3_arb}.

  • deployer (eth_account.signers.local.LocalAccount) – The deployer account. A separate HotWallet is created per chain for nonce management.

  • chain_configs (dict[str, eth_defi.erc_4626.vault_protocol.lagoon.deployment.LagoonConfig]) – Per-chain LagoonConfig instances. Keys must match chain_web3 keys. All configs must have the same safe_salt_nonce set. The parameters.underlying field is auto-resolved per chain from eth_defi.token.USDC_NATIVE_TOKEN if set to a zero/empty address. Set max_settlement_amount independently on each non-satellite config to enable the atomic cumulative gross-settlement window safety feature for that chain’s Lagoon vault.

  • max_workers (Optional[int]) – Maximum number of parallel deployment threads. Defaults to the number of chains.

  • lighter_activation (LagoonLighterActivation | None) – Optional coordinated hub subscription, CCTP funding and Ethereum satellite activation. All contract workers finish before funding and owner finalisation follows verified key registration. The protected progress file supports explicit manual recovery after interruption.

Returns

LagoonMultichainDeployment with per-chain results.

Return type

eth_defi.erc_4626.vault_protocol.lagoon.deployment.LagoonMultichainDeployment