Introduction
MORE is an open and extensible framework for digital asset management. An ecosystem of 2 core protocols, MORE Markets and MORE Vaults, it is designed to make DeFi more accessible, cheaper, more secure and more flexible for professional asset managers and depositors.
Protocol at a Glance
MORE Vaults is a trust-minimised vault framework that lets any asset manager spin up bespoke yield strategies while keeping user deposits inside an upgrade-safe, ERC-4626–compatible container. A new vault is born by sending a facet bundle to the Vaults Factory, which mints a fresh Diamond proxy and whitelists it in the Vaults Registry. From that moment on:
Users get a “set-and-forget” ERC-20 share token; deposits are handled by the shared
VaultFacet, withdrawals respect ERC-4626 accounting logic.Managers retain granular control over rebalancing, fees, and capacity via dedicated configuration facets, without ever touching the core deposit/withdraw paths.
The protocol enforces a single, auditable deployment path (factory ➝ registry ➝ diamond), making it trivial for explorers and risk dashboards to verify that a vault is “official”.
The end result is a permissionless assembly line where professional strategists can iterate rapidly, and depositors can shop for risk/reward profiles without reading Solidity.
Guiding Principles
Permissionless & Permissioned
The PermissionlessVaultsRegistry treats every facet as whitelisted and disables fees, so anyone can launch a vault without asking for protocol approval. The PermissionedVaultsRegistry is managed by MORE DAO and proposes a Registry of approved facets.
Trust-minimised custody
User assets never sit in a strategist’s EOA; they live in an immutable, non-custodial, Diamond proxy whose logic is upgrade-gated by the factory’s diamondCutFacet.
Role-based governance
Each vault stores owner, curator, and guardian addresses in a single library slot; runtime modifiers in AccessControlLib validate them, ensuring only authorised parties can update strategies or pause the vault.
Configurable safety rails
The ConfigurationFacet caps TVL, enforces deposit whitelists, and applies timelocks to fee changes—giving depositors measurable boundaries on manager behaviour.
Transparent fail-fast errors
Custom reverts like InvalidSelector, UnsupportedAsset, or AllFacetsAllowedByDefault are returned in a plain text, making front-end UX clear and audits easier to reason about.
Composability first
Every external dependency, Aave, Curve, Uniswap, Chainlink, lives behind a clean interface namespace so facets can be swapped out without breaking other modules.
Depositor trust model: The protocol eliminates custody risk but not governance risk; depositors must still evaluate the manager roles and strategy logic of each vault they choose to enter.
Jump right in
Last updated
