Vaults Framework
MORE Vaults is an open‑source cross-chain vault standard that combines the composability of the ERC‑2535 Diamond Standard with a rigorously audited, invariant and generic core. By separating the asset-critical logic from the ever‑evolving strategy layer, MORE drives down implementation and security costs for strategists, integrated protocols, and depositors alike.
The inspiration and motivation behind MORE Vaults stems from liquidity providers' need for a set-it-and-forget-it DeFi venue similar to those provided by mutual funds, hedge funds and ETFs in TradFi. MORE offers significantly better capital efficiency as well as stickier liquidity through:
An omni-chain vault core - the same vault deployed as a mesh across any EVM;
A bridge-agnostic interface - transfers assets securely within the same vault mesh;
Shares as omni-chain tokens - depositors choose the chain on which they hold the receipt token;
Adding and removing protocol and strategy integrations as your portfolio evolves;
Running multiple strategies or farms in parallel or composing liquidity across venues;
A bundler for atomic transactions bounded by configurable safeguards;
Fully on-chain execution and accounting for 100% NAV and execution transparency.
Why MORE matters?
Modularity
Every capability lives in its own facet so vault managers can swap them in or out without touching the core.
Openness
Anyone can launch a vault or use any integration. The DAO merely approves and verifies their safety.
Resilience
The core facets are upgradeable, formally verified, and protected by a time‑locked upgrade gate.
Ecosystem
Common event formats, SDKs, and a public subgraph let frontends, dashboards and analytics integrate once to support all vaults.
Design Principles
Transparency
On‑chain everything. Asset accounting follows ERC‑4626 and lives trustlessly, entirely on‑chain. Auditable and verifiable protocol integrations communicate directly with the core.
Diamond Loupe introspection. Every vault exposes a selector table that users and auditors can query to see exactly which functions exist, who can call them, and when they were added.
Public registries. A canonical registry records deployed vaults and permissioned integrations and oracles, all packaged in a subgraph for auditors, explorers and risk dashboards.
Upgradability
Scoped upgrades. The vault core is upgradeable in order to quickly and iteratively improve core functionality. Core upgrades are optional to vault owners, but recommended. Vault Owners are free to upgrade their own non-core facets.
Timelocks. Vault allocations, rebalances, changes to the rules, governance or risk parameters of the vault are timelocked, giving users a chance to exit before any new code executes.
Safe migrations. Users' assets and shares are migrated between vault versions without breaking ERC‑4626 compatibility.
Trust‑Minimization
Permissionless deployment. Anyone can call CreateVault on the factory, pick from audited or experimental facets, and launch in a single transaction.
No gate‑keeping. The DAO maintains permissioned registries and whitelists audited facets, protocols and oracles. Frontends decide what to surface, but niether the protocol nor the DAO ever explicitly censors.
Last updated