MetaVaults in Different Flavors Now Open to Everyone
StakeWise launches major MetaVaults upgrade! 🎉
When we first introduced MetaVaults, we set out to scale staking: rather than running validators directly, a MetaVault routes deposits across sub-vaults according to the curator contract’s strategy — enabling new staking patterns and competitive returns.
With this release, any operator can now deploy a MetaVault, choose from public, private, and ERC-20 variants, redeem osETH against MetaVault-backed positions, and nest MetaVaults inside one another.
For technical details and security verification, see the release notes and our security audit report.
Let's dive in.🤓
Permissionless MetaVault Deployment
MetaVault factories on Ethereum and Gnosis are now permissionless: any operator can launch a MetaVault without going through StakeWise governance — bringing them in line with how regular Vaults have always worked.
A Cleaner Architecture
Sub-vault bookkeeping now lives in its own SubVaultsRegistry contract, deployed per MetaVault via SubVaultsRegistryFactory. The registry owns everything sub-vault-related — the curator address, the set of sub-vaults, their states, exit queues, and harvest accounting — while the MetaVault keeps only a pointer to it and forwards calls.
The benefits are tangible: a smaller, easier-to-audit MetaVault contract; sub-vault state isolated in its own storage layout; and a foundation that makes adding new sub-vault features straightforward, without touching core Vault accounting code.
ERC-20 MetaVault Variants
Three new MetaVault types are now live on Ethereum:
Public ERC-20 MetaVault — shares are a fully transferable ERC-20 token, usable across DeFi.
Private ERC-20 MetaVault — the same, but whitelisted to permissioned participants.
Private MetaVault — whitelisted, with non-transferable shares.
The two private variants give operators the flexibility to match their compliance setup.
osETH Redemptions for MetaVaults
osETH positions backed by a MetaVault can now be redeemed through the protocol's redemption mechanism.
A quick refresher on how redemption works: holders deposit osETH into the OsTokenRedeemer; the redeemer burns that osETH against eligible borrower positions in a Vault — reducing the borrower's debt and collateral, and pulling the released stake into the redeemer for holders to claim at the protocol exchange rate. MetaVaults, however, don't hold stake directly — their capital is staked across a set of sub-vaults — so there's no borrower position at the MetaVault layer to redeem against.
The new flow reuses the same redemption primitive but routes it through the MetaVault’s SubVaultsRegistry, which decides which sub-vaults to draw from and how much from each. In the same transaction, the MetaVault mints osETH against its own sub-vault deposit (capped by the sub-vault's LTV), and the redeemer uses that osETH to redeem against the sub-vault — closing the MetaVault’s temporary borrowing position and releasing stake up to the MetaVault. From there, the standard redemption path completes as it would against any regular Vault.
Nested MetaVaults
MetaVaults can now delegate to another MetaVault as a sub-vault, letting operators build layered strategies — a top-level MetaVault spreading across themed MetaVaults — without deploying custom contracts. A propose / accept / reject flow, gated by the StakeWise DAO, prevents accidental or hostile nesting.
The composition possibilities are wide open, and we're excited to see what operators build.🔨
Technical Improvements
More accurate MetaVault share price. MetaVaults now track assets that have exited sub-vaults but haven't yet been settled, so share price stays accurate between harvests, and deposits and withdrawals always price fairly.
Redemptions no longer blocked unfairly. A bug in exit-queue accounting was gating some withdrawals even when enough assets were available.
BalancedCurator respects sub-vault capacities. The DAO-approved curator that spreads deposits evenly across sub-vaults now honors each sub-vault's configured limit, instead of overflowing a single sub-vault and reverting.
Harvest check is skipped for uncollateralized MetaVaults. A MetaVault can now be set up and populated with sub-vaults before it has any validators of its own, instead of being blocked by a harvest requirement that doesn't yet apply.
For full details, see the release notes.
Final Thoughts
This update marks a turning point for MetaVaults: they become a primitive anyone can deploy and build on. A wider design space for operators, more options for stakers, and more flexibility for the Ethereum staking ecosystem as a whole.
