Vault curation
Curators define what a vault will and will not accept, publish the policy on chain, and earn a fee on the yield they generate. Depositors keep custody throughout.
Set the mandate
Choose collateral types, oracles, loan-to-value ceilings and liquidation parameters. The mandate is stored on chain and enforced by the vault, not by trust.
Publish the policy
Allocation limits and rebalancing rules are public and versioned. Depositors see exactly what a curator can and cannot do before committing funds.
Earn on performance
Curators set a fee on generated yield, capped by the vault at deployment. The cap is immutable, so a fee cannot be raised after deposits arrive.
What a curator controls
A curator selects which markets the vault may allocate to and the maximum exposure for each. They can reduce a cap immediately, and increase one only after a timelock that gives depositors a window to exit first. That asymmetry is deliberate: tightening risk is instant, loosening it is never a surprise.
What a curator cannot do
Curators never take custody. They cannot withdraw depositor funds, redirect them to an address of their choosing, allocate outside the published mandate, or raise the fee above the deployment cap. Every one of these is a contract-level constraint rather than a policy commitment.
Confidential by default
Deposits routed through the shielded pool keep the depositor's identity and position size private while still counting toward the vault's public totals. A curator sees the aggregate they are managing; they do not see who is behind it.
Getting started
Curation is permissionless — deploying a vault requires no approval from us. Read the vault interface in the developer documentation, then deploy from the app. Established curators can request a listing review to appear in the curated directory.