Create your vault
Step-by-step instructions to create vault.
Lagoon Vault Factory
The Lagoon Vault Factory is the core smart contract that enables permission-less deployment of on-chain Lagoon Vaults. It allows anyone to create a fully customizable vault across supported chains.
You can find the supported chains and factories addresses here.
Currently, vault creation is only possible via etherscan.
Before launching a vault, feel free to deploy a test vault on Arbitrum using the following Factory here.
Vault Deployment Function: createVaultProxy
createVaultProxycreateVaultProxy is the function used to deploy a new Lagoon Vault from the Factory contract.
Etherscan based scan have some bugs. Put double quotes around your addresses and strings in the _init(tuple) object. Like this: "0x0000000000000000000000000000000000000000"
Create Vault Proxy Parameters
Upgradability parameters
_logic (address) – This is the address of the logic of your contract. Your vault is a proxy that will use another contract logic. If you don't want to use the default version of the vault, you can supply the address of another authorized logic. If you want to use the default version, put the address 0.
To use the default vault version, put:
0x0000000000000000000000000000000000000000_initialOwner (address) – The address that will be capable of upgrading the vault version. This address will be the owner of the ProxyAdmin, a contract deployed at the proxy construction. If you want your vault to be immutable, you can renounce the ownership of this ProxyAdmin contract by calling renounceOwnership(). This action is irreversible.
_initialDelay (uint256) – Delay required to wait to update a vault. Expressed in seconds. The minimum value is 86400 seconds (24 hours). The max value is 2592000 seconds (1 month). You can edit this delay, again after waiting the delay itself.
Underlying Asset
underlying (address) – The address of the underlying asset (ERC20 token) for which the vault is being created.
The Valuation Oracle (valuationManager) will be providing the valuation of the vault in this unit of account.
This token can not be a rebasing token such as stETH or Aave debt token. In the case of stETH you would use it's non-rebasing equivalent, wstETH.
The valuation manager will be providing the valuation of the vault in this unit of account.
The vault will manage deposits and withdrawals in this asset.
Vault General Parameters
name (string) – The name you want to give to the ERC-20 shares. Immutable
symbol (string) – The ERC-20 shares symbol. Immutable.
enableWhitelist (boolean) – Restrict vault access to approved addresses. Put 0 for false and 1 for true. Can be enabled during initial setup only.
Whitelist can only be activated at vault creation. Deactivation can happen anytime and is irreversible.
If activated, the list itself can be edited anytime.
If the whitelist is enabled, you can add and revoke addresses usingaddToWhitelist and revokeFromWhitelist.
Roles & Governance Setup
safe (address) – Curation address that holds the Vault’s assets. It is referred as curation address in the doc. This variale is immutable. Any curation solution is compatible including:
Safe Multisig – Safe {Wallet}
MPC - Multi-Party Computation wallet
EOA - Externally Owned Account wallet
This is the address that will manage the vault positions and validate Valuation.
admin (address) – Address with administrative privileges. The Vault Admin role is responsible for managing the governance structure that will rules the vault. The admin has significant control over the vault's key parameters and security features, defining how it operates and is governed.
valuationManager (address) – The Valuation Oracle role provides updated valuations of the vault total assets.
whitelistManager (address) – The Whitelist Manager role controls which addresses are authorized to interact with the vault.
If enableWhitelist is false, please provide a null address value :
0x0000000000000000000000000000000000000000Fees Parameters Setup
feeReceiver (address) – Address where fees will be sent at each settlement.
managementRate (uint16) – Percentage of fee charged for vault operation, express in basis points.
performanceRate (uint16) – Percentage of fee charged on performance gains, express in basis points.
rateUpdateCooldown (uint256) – Amount of time before a fee rate update takes effect (in second). Immutable.
Technical Parameter
salt (bytes32) – A unique value in bytes32 to used in conjunction with the vault's other parameters to deterministically generate its address.
Vault Deployment Result
When the createVaultProxy transaction is executed, it results in the deployment of three smart contracts:
Transparent upgradeable proxy This is the main contract representing your Vault. It manages deposits, withdrawals, valuations, settlements, and fees. It is also the ERC20 address of the recept token representing a share of the vault.
Silo Contract This contract is where pending deposits and withdrawals tokens (underlying and shares) are stored.
Proxy Admin
This contract is the admin of the Transparent Upgradeable Proxy. Through it, you can upgrade your vault logic. The owner of this contract is the address supplied at deployment: _initialOwner.
Example: Vault Deployment Output
Upon successful execution, you will see 3 new contracts addresses returned—one for the Vault Proxy, one for ProxyAdmin and one for the Silo.
You must complete the Post-Deployment Operations to finalize your Vault setup.
Last updated