Mellow Core
This review cannot reach a judgment on Mellow. Its vault infrastructure is well designed: isolated subvaults paired with verifier contracts that list the exact calls each execution path may make, a detailed on-chain role system that outside reviewers can inspect, and coverage from six independent audit firms across its history. Mellow has operated since 2022 through G3M Labs S.A., but this review could not confirm that entity’s jurisdiction. The Terms of Service document that would state it blocks automated access. Separately, the live application actively restricts requests by IP and points users to those same unreachable Terms of Service. This may reflect a US-person block or another access policy, but this review could not tell which. Redemption follows a two-step process that depends on the curator. Shares burn at once when requested, but liquidity settles later, based on the curator’s ability to unwind subvault positions. This exit process is less certain than an atomic, on-demand redemption.
- G3M Labs S.A.’s incorporation jurisdiction and the scope of the IP-access restriction are publicly disclosed and confirmed not to reflect a US-person exclusion
- A canonical list of live vault owners and their per-vault admin, multisig, and timelock configuration is published
- Redemption settlement timing is disclosed as a specific, bounded figure per major vault rather than an open-ended curator-dependent process
- Incident history for Mellow-built vaults is independently verified with working search tooling
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-19.
The research file
Mechanism
Mellow provides vault infrastructure, not one product. Third parties configure “Core Vaults” or “Flexible Vaults” tracked by a depositor’s ERC-4626-style share. Each Subvault is a separate execution unit paired with a Verifier contract that limits the exact calls it may make. This contains a failing strategy instead of letting it affect other allocations in the same vault. Strategies vary by vault and include legacy EigenLayer-restaking tooling (now deprecated), DVT staking, cross-chain positions, and active liquidity management. A Mellow vault that wraps a restaking position has two layers of risk: risk from Mellow’s vault and curator, plus risk from the base protocol, such as EigenLayer or another venue, where the curator has allocated funds.
The undisclosed jurisdiction and access restriction
A copyright notice names G3M Labs S.A. as the operator. This review could not confirm its jurisdiction of incorporation because the Terms of Service PDF that would state it returned an IP-restriction error on every fetch attempt, including a headless-browser workaround. The error itself told users to “check Terms of Service,” but the same restriction blocked that document. This review could not determine whether the policy blocks US persons, a broader set of sanctioned jurisdictions, or something else. A registry that serves US advisor clients cannot state who may use a product when it cannot read the product’s own access policy.
Control
Mellow controls access through more than 60 detailed roles listed on-chain and set by vault, strategy, and action. Each vault’s owner can configure its emergency pause, multisig control, and timelocked parameter changes. A single Mellow-wide admin key does not control them. Control quality therefore varies by vault instead of staying uniform across the protocol. Public documentation did not provide a standard list of vault-owner identities or their specific multisig setups. A Risk Manager can also correct vault balances directly to account for oracle drift. That discretionary power warrants attention despite the otherwise strong on-chain permission design.
Redemption
Deposits and redemptions use time-buffered queues instead of settling at once. When a depositor requests redemption, the shares burn at once and cannot be restored. Mellow designed this step to prevent yield-griefing attacks. But the assets arrive later because the curator must unwind subvault positions before releasing liquidity, subject to a configurable `redeemInterval`. For a vault built on restaking, the effective redemption time includes the base protocol’s own unbonding period as well as the interval set by the vault owner. Mellow describes this as liquidity risk managed by the curator, not a guarantee enforced by the protocol.
Track record and comparison
Tracked chain-level TVL peaked near $497M on Ethereum in December 2024 and now sits around $232M across Ethereum, Monad, Mezo, and RSK. Mellow’s marketing cites a $1B all-time peak across its full product history, which covers more than this chain-level series. This review could neither confirm nor rule out a specific incident or depeg involving a Mellow-built vault within its search coverage. Compared with the curator-vault models of Morpho or Euler, Mellow supports more types of strategies across DeFi and CeFi rather than focusing on lending alone. But its two-step redemption depends on the curator, making liquidity less certain than Morpho Blue’s generally near-instant exit, which remains subject to utilization.
Sources
The claims above trace to these. Where a number could not be independently verified, the thesis says so.
- Mellow Protocol — homepage and product overview · primary · accessed 2026-08-19
Supports: vault infrastructure framing, subvault isolation and verifier design, per-vault admin and pause configuration - Mellow documentation — core vaults architecture · primary · accessed 2026-08-19
Supports: role-based access control system, deposit and redeem queue mechanics, Risk Manager discretionary balance correction - Mellow documentation — security and audit history · primary · accessed 2026-08-19
Supports: StateMind, ChainSecurity, Sherlock, MixBytes, Nethermind, and Decurity audit coverage - DefiLlama — Mellow Core protocol data · secondary · accessed 2026-08-19
Supports: chain-by-chain TVL history and peak figures - Mellow Protocol — GitHub organization · primary · accessed 2026-08-19
Supports: open-source contract repositories, BUSL-1.1 license
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 |
|---|---|---|---|
| Ethereum | Approved | No freeze key | No sequencer, no upgrade key, no operator who can be compelled. Rule changes require social consensus. |
| Monad | Approved with limits | Governed, no freeze | the L1 has a public validator path, but its short production record, single initial client lineage, and Foundation-directed delegation keep stake and operations concentrated. |