Summary: Mellow is a vault framework for deploying curated onchain products where the key design surface is not generic yield aggregation but constraint-enforced strategy execution. Its current docs make the protocol look like a programmable vault layer that lets curators actively manage strategies while keeping integrations, permissions, capital movement, oracle checks, and withdrawal logic bounded by onchain configuration. The restaking-specific product lines matter, but the deeper mechanism is the separation of depositor capital from curator discretion through vault-level guardrails.
What it does:
Provides Core Vaults as the main architecture for curated onchain structured products with explicit permissions, execution rules, and risk limits
Supports several vault families, including Core Vaults, MultiVaults, Interoperable Vaults, Simple LRT, DVstETH / DVV, and Mellow ALM
Lets curators operate strategy logic while constraining them through vault configuration rather than giving free-form offchain mandate power
Extends the vault model into restaking and cross-chain contexts through aggregated subvaults, LayerZero-based cross-chain flows, and queued-withdrawal LRT designs
Publishes open-source vault repositories showing earlier permissionless multi-token rebalancing vaults and newer flexible-vault architecture with contract-level modules for permissions, queues, managers, hooks, and oracles
Key claims:
The docs describe Mellow as providing vault smart-contract primitives for curated onchain products with explicit risk constraints and defined execution surfaces
The Core Vault docs say strategy constraints are encoded directly into configuration, covering allowed integrations, permitted actions, and how capital can move between execution paths, with enforcement onchain
The broader vault overview says each product line maps to a different operating pattern: isolated programmable vaults, aggregated subvault frameworks, cross-chain vaults, queued-withdrawal LRTs, DVT-based staking exposure, and AMM liquidity management
The docs explicitly frame curators as active operators whose authority is bounded by permissions, limits, and execution rules rather than by broad discretionary mandates
The public GitHub repositories reinforce that this is a real vault-engineering effort, not only a front-end product: Mellow publishes code and architecture around vaults, strategies, modules, queues, permissions, and rebalancing flows
The strongest mechanism insight is that Mellow is trying to standardize a curator-controlled but contract-bounded product layer for restaking and structured yield, which makes it a useful comparison point for Veda-style vault control planes and Symbiotic-adjacent restaking packaging
Whitepaper: No canonical standalone whitepaper or litepaper surfaced in this pass. The clearest primary materials were Mellow’s official docs plus the public vault repositories; see ../whitepapers/mellow-primary-sources-2026-05-08.md.