deploy_automated_lagoon_vault
Documentation for eth_defi.lagoon.deployment.deploy_automated_lagoon_vault function.
- deploy_automated_lagoon_vault(web3, deployer, asset_manager, parameters, safe_owners, safe_threshold, uniswap_v2, uniswap_v3, any_asset=False, etherscan_api_key=None, use_forge=False, between_contracts_delay_seconds=10.0)[source]
Deploy a full Lagoon setup with a guard.
Lagoon automatised vault consists of
Safe multisig - we use 1.4.1 here
Vault module
Lagoon protocol smart contracts
TradingStrategyModuleV0 module enabling guarded automated trade executor for the Safe
For roles - Asset manager (Trading Straegy) and Valuation Manager (Lagoon) are the same role - Any Safe must be deployed as 1-of-1 deployer address multisig and multisig holders changed after the deployment.
Warning
Because we need to mix Forge, Safe lib and Web3.py transaction nonce management becomes a madness.
Note
Deployer account must be manually removed from the Safe by new owners.
- Parameters
web3 (web3.main.Web3) –
deployer (eth_account.signers.local.LocalAccount | eth_defi.hotwallet.HotWallet) –
asset_manager (eth_typing.evm.HexAddress) –
parameters (eth_defi.lagoon.deployment.LagoonDeploymentParameters) –
safe_owners (list[Union[eth_typing.evm.HexAddress, str]]) –
safe_threshold (int) –
uniswap_v2 (eth_defi.uniswap_v2.deployment.UniswapV2Deployment | None) –
uniswap_v3 (eth_defi.uniswap_v3.deployment.UniswapV3Deployment | None) –
any_asset (bool) –
- Return type