Create Your Vault

Step-by-step instructions to create vault.

Lagoon Vault Factory

The Lagoon Vault Factory is the core smart contract that enables permissionless deployment of on-chain Lagoon Vaults. It allows anyone to create a fully customizable vault across supported chains.

Each vault is deployed as a unique instance with configurable parameters. Each Vault is created as an independent smart contract with customizable settings.

Factory Smart Contract

The table below lists the Lagoon Vault Factory contract addresses for each supported network.

Chain	Factory Address
Ethereum	https://etherscan.io/address/0x09C8803f7Dc251f9FaAE5f56E3B91f8A6d0b70ee#writeContract#F2
Arbitrum	https://arbiscan.io/address/0x58a7729125acA9e5E9C687018E66bfDd5b2D4490#writeContract#F2
Base	https://basescan.org/address/0xc953fd298fdfa8ed0d38ee73772d3e21bf19c61b#writeContract#F2
Unichain	https://uniscan.xyz/address/0xaba1a2e157dae248f8630ca550bd826725ff745c#writeContract#F2
Berachain	https://berascan.com/address/0x7cf8cf276450bd568187fdc0b0959d30ec599853#writeContract#F2
Sonic	https://sonicscan.org/address/0x99cd0b8b32b15922f0754fddc21323b5278c5261#writeContract#F2

Vault Deployment Function: createVaultProxy

createVaultProxy is the function used to deploy a new Lagoon Vault from the Factory contract.

Create Vault Proxy Parameters

Underlying Asset

underlying (address) – The address of the underlying asset (ERC20 token) for which the vault is being created.

The valuation manager will be providing the valuation of the vault in this unit of account.

The vault will manage deposits and withdrawals of this underlying asset.

---

Vault General Parameters

name (string) – The human-readable name of the vault. It is used primarily for display and identification purposes.

symbol (string) – The ERC-20 token symbol representing depositors' shares in the vault.

enableWhitelist (boolean) – Restrict vault access to approved addresses.

💡 Value for enableWhitelist is :

• 0 if false

• 1 if true

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 true, please provide an initial whitelist into the Vault, after deployment, from the function addToWhitelist (0x7f649783).

---

Roles & Governance Setup

safe (address) – Wallet address that holds the Vault’s assets. Any wallet type is compatible including:

• Safe Multisig – Safe {Wallet}
• MPC - Multi-Party Computation Wallet

• EOA - Externally Owned Account Wallet

This is the address where underlying assets are sent after settlement when net deposits exceed withdrawals, and from which assets are pulled when net withdrawals exceed deposits.

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 Price Oracle role provides updated valuations (NAV) of the Vault for fair deposits and redemptions.

Can be a multisig (manual updates) or a smart contract (automated pricing algorithm).

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 :

0x0000000000000000000000000000000000000000

---

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

💡 Fees are expressed in basis points (bps)

• 0.5% = 50 bps

• 2% = 200 bps

• 15% = 1500 bps

rateUpdateCooldown (uint256) – Amount of time before a fee rate update takes effect (in second).

💡 Value is in seconds (e.g., 3600 for 1 hour).

---

Technical Parameter

salt (bytes32) – A unique value in bytes32 to used in conjunction with the vault's other parameters to deterministically generate its address. This ensures the uniqueness of the vault's address even if other parameters are identical.

💡 Value in hexadecimal : e.g.0x24

---

Vault Deployment Result

When the createVaultProxy transaction is executed, it results in the deployment of two smart contracts:

• Vault Contract 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 (underlaying and shares) are stored allowing for simplification of the accountability in the vault.

Example: Vault Deployment Output

Upon successful execution, you will see 2 new contract addresses returned—one for the Vault and one for the Silo.

You must complete the Post-Deployment Operations to finalize your Vault setup.