Mellow Core

Rejected venues wait the longest for re-review; a rejection has to earn another look before the scheduled date.

REJECTED ON AN UNDISCLOSED JURISDICTION AND AN ACCESS RESTRICTION THIS REVIEW COULD NOT CHARACTERIZE. Mellow is genuinely well-architected vault infrastructure: isolated subvaults paired with verifier contracts that whitelist exactly which calls each execution path can make, a granular on-chain role system enumerable for external audit, and coverage from six independent audit firms across its history. Live since 2022 and operated by G3M Labs S.A., that entity’s jurisdiction could not be confirmed because the Terms of Service document that would state it is itself blocked from automated access — and separately, the live application actively IP-restricts requests with a message pointing back to that same unreachable Terms of Service, which may indicate a US-person block or some other access policy this review could not distinguish. Redemption is a two-step, curator-dependent process — shares burn immediately on request but liquidity settlement is asynchronous, timed to the curator’s ability to unwind subvault positions — a materially different and less certain exit mechanic than an atomic, on-demand redemption.

Kill criteria: the events that revoke this verdict
• 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

The research file

Mechanism

Mellow is vault infrastructure, not a single product: third parties configure ”Core Vaults” or ”Flexible Vaults” that a depositor’s ERC-4626-style share tracks. Each Subvault is a walled execution unit paired with a Verifier contract restricting exactly which calls it can make, so a failing strategy is contained rather than contaminating other allocations within the same vault. Underlying strategies vary by vault — legacy EigenLayer-restaking tooling (now deprecated), DVT staking, cross-chain positions, and active liquidity management. A vault built on Mellow that wraps a restaking position carries two stacked risk layers: Mellow’s own vault and curator risk, plus whatever base protocol (EigenLayer or another venue) the curator has actually allocated into.

The undisclosed jurisdiction and access restriction

The operating entity, per a copyright notice, is G3M Labs S.A.; its jurisdiction of incorporation could not be confirmed because the Terms of Service PDF that would state it returned an IP-restriction error on every fetch attempt, including a headless-browser workaround, with the error message itself directing users to ”check Terms of Service” — a document the same restriction blocks from being read. Whether this is a US-person block, a broader sanctions-jurisdiction block, or something else could not be determined. A registry serving US advisor clients cannot record eligibility for a product whose own access-restriction policy is unreadable.

Control

Access control runs through a role-based permission system with over 60 granular, on-chain-enumerable roles scoped per vault, per strategy, and per action. Emergency pause, multisig control, and timelocked parameter changes are configurable per vault by each vault’s own owner, not centralized under a single Mellow-wide admin key — meaning control quality varies vault by vault rather than being uniform across the protocol, and no canonical list of vault-owner identities or their specific multisig configurations was found in public documentation. A Risk Manager role can also directly correct vault balances to account for oracle drift — a discretionary lever worth flagging alongside the otherwise strong on-chain permission design.

Redemption

Deposits and redemptions both flow through time-buffered queues rather than settling atomically. On redemption, a depositor’s shares burn immediately and irreversibly — a design meant to prevent yield-griefing attacks — but liquidity settlement is asynchronous, requiring the curator to unwind subvault positions before assets are actually released, gated by a configurable `redeemInterval`. For a vault built on restaking, effective redemption time is bounded by the underlying protocol’s own unbonding period on top of whatever interval the vault owner has set — Mellow frames this as curator-managed liquidity risk rather than a protocol-enforced guarantee.

Track record and comparison

Tracked chain-level TVL peaked near $497M on Ethereum in December 2024 and currently sits around $232M across Ethereum, Monad, Mezo, and RSK; Mellow’s own marketing cites a $1B all-time peak across its full product history, a figure broader than what this chain-level series captures. No specific incident or depeg involving a Mellow-built vault could be confirmed or ruled out in this review’s search coverage. Against Morpho or Euler’s curator-vault models, Mellow’s differentiator is a wider strategy surface — explicitly multi-venue across DeFi and CeFi rather than single-purpose lending — but its two-step, curator-dependent redemption is a meaningfully different and less certain liquidity profile than Morpho Blue’s generally near-instant, utilization-gated exit.

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 verdict above grades the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The least safe layer sets the position’s grade, and the position table names which one that is.