Midas powers Ether.fi’s second Liquid RWA vault in partnership with Plume Network
Ether.fi commits $100M to the new vault, giving its $6B deposit base access to institutional-grade real-world asset yields.
Share
Add us on Google by Editorial Team Jun. 6, 2026Ether.fi just dropped $100 million into a new Liquid RWA vault built on Midas’ Vault OS infrastructure, marking the second time the restaking giant has tapped Midas to power one of its vaults. The product, launched June 5 in collaboration with Plume Network, gives ether.fi’s users access to tokenized yields from traditional financial instruments like overcollateralized credit pools, AAA-rated CLOs, and bond ETFs.
The $100M commitment comes from the protocol’s existing managed capital and liquidity provider base, which now exceeds $6 billion in total customer deposits.
AdvertisementWhat the vault actually does
Users access the vault directly through the ether.fi interface, no need to leave the platform or navigate a separate protocol. Under the hood, Midas’ Vault OS handles the infrastructure, while Plume Network’s Nest Vaults provide the underlying framework for real-world asset exposure.
This isn’t ether.fi’s first foray into Plume’s ecosystem. The protocol previously invested $25 million into Plume’s Nest protocol, specifically targeting nBASIS vaults. The new $100M allocation represents a fourfold increase in that commitment.
The first ether.fi vault built on Midas’ Vault OS was the EURC Liquid vault, launched around May 2026 in partnership with K3 Capital.
What this means for investors
The risk side of the equation deserves attention. Tokenized RWAs inherit the credit risk of their underlying assets, and while AAA-rated CLOs have performed well historically, they’re not immune to broader market stress. Investors accessing these products through ether.fi’s vault should understand they’re not getting the same risk profile as staking ETH — they’re getting exposure to an entirely separate set of economic factors.
Disclosure: This article was edited by Editorial Team. For more information on how we create and review content, see our Editorial Policy.
