Mezo Vaults
Mezo Vaults issue receipt tokens while a named strategist deploys deposits into lending, real-world-credit, or other DeFi strategies. The August 15, 2026 survey reported about $7.57M on Mezo, but delegated allocation is the more fundamental rejection: the live venue and strategy can differ by vault and can be managed after deposit without a client-enforceable approved-protocol list. Reopen only for a named vault with fixed client-compatible limits and independently verifiable holdings, roles, losses, and exits.
- A named vault enforces a client-compatible immutable allowlist and caps, with independently verifiable holdings, roles, losses, valuation, and stressed withdrawal liquidity
Watched nightly: a warning on its venues or files, or a cited document that changes, reopens the memo. The first confirmation is due 2026-11-15.
The research file
Mechanism and class applicability
Mezo documents a vault flow in which the user deposits MUSD, BTC or another supported asset, receives a receipt token, and delegates deployment to the named strategist. Mezo-operated and external partner vaults can use different lending, real-world-credit or other DeFi strategies. That continuing strategy and venue selection directly satisfies the v1 delegated-allocation dossier.
Current observation and perimeter
The DefiLlama protocol API read on 2026-08-15 classified Mezo Vaults as a Yield Aggregator and reported approximately $7.57M on Mezo. Official materials list Mezo-managed savings and lending vaults alongside external vaults from partners such as August, UWI and Upshift, so the aggregate slug is not one stable underlying position.
Control, loss and exit applicability
The strategist rather than the receipt holder selects and operates the underlying strategy; Mezo expressly says it does not control external partner strategies. Each receipt therefore inherits the active contracts, assets, counterparties, valuation and withdrawal mechanics, while the aggregate protocol label does not let an adviser enforce a fixed venue allowlist or stressed-exit limit.
Why the shared dossier decides
The v1 delegated-allocation dossier controls regardless of current size because the adviser cannot pin the client to a continuously approved set of underlying exposures. Reopen only for a named vault whose immutable or client-specific allowlist and caps contain approved venues, with live holdings, debt, privileged roles, realized losses, valuation and executable withdrawal liquidity independently verifiable.
Class rule
The delegated allocation class is outside the approved structures, so every protocol in it is not approved until the rule changes. The rule is about the structure, not an adverse finding about this protocol, and it is not a client instruction. The events that would reopen it are listed with the memo.
Sources
The claims above trace to these. Where a number could not be independently verified, the thesis says so.
- Mezo — Vaults overview · primary · accessed 2026-08-15
Supports: receipt token, strategist deployment, Mezo vaults, external partner vaults, strategy risk - Mezo — Earn product overview · primary · accessed 2026-08-15
Supports: structured strategies, vaults, pools, Mezo chain - Mezo — current ecosystem and vault examples · primary · accessed 2026-08-15
Supports: Morpho vaults, UWI RWA vault, MUSD savings vault, external strategies - DefiLlama — Mezo Vaults survey record · secondary · accessed 2026-08-15
Supports: current TVL, Mezo perimeter, Yield Aggregator category
Inherited controls
The research above describes the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The layer with the most administrative power sets the position’s effective control; that describes control, not quality or suitability.
| Chain | Verdict | Control | Control constraint |
|---|