Vaults Framework

MORE Vaults is an open‑source 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 motiviation behind MORE Vaults stems from depositors' need for a set-it-and-forget-it DeFi venue similar to those provided by mutual funds, hedge funds and ETFs in TradFi. For strategists, adding and remove protocol integrations, combining multiple strategies and migrating liquidity atomically within the same vault offers significantly better capital efficiency as well as stickier liquidity.

While MORE Vaults are not yet cross-chain, this feature is currently in development and will extend vault capabilities such as liquidity migration and on-chain aggregated accounting to multi-chain implementations. The target release date for this feature is Q3 2025.

Why MORE matters?

Modularity	Every capability lives in its own facet so vault managers can swap it in or out without touching the core.
Openness	Anyone can launch a vault or publish an integration. The DAO merely approves and verifies their safety.
Resilience	The core facets are immutable, 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 entirely on‑chain. No hidden keeper scripts, off‑chain merkle roots, or validator committees.

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 registry & dashboards. A canonical registry records vault metadata, facet audit links, oracles, whitelists, strategy audit links, etc., feeding real‑time data to explorers and risk dashboards.

Upgradability

Scoped upgrades. The DAO may only modify core facets via a 48‑hour timelock. Vault creators may only upgrade their own strategy facets.

Timelocks. If a new facet is added or a strategy is upgraded, withdrawals stay enabled giving users a chance to exit before any new code executes.

Safe migrations. A helper contract migrates user positions between major core 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 one transaction.

No gate‑keeping. The DAO maintains both permissioned and permissionless facet and selector registries and whitelists audited facets in the permissioned registry. Frontends decide what to surface, but niether the protocol nor the DAO ever explicitly censors.

Cryptoeconomic alignment. When the MORE token launches, facet authors and strategists must stake MORE. They will earn a share of protocol fees in MORE token proportionately to the value in thier respective deployments. Slashing penalties fund an insurance pool if their code violates declared invariants.