Mellow

Imagine building your own institutional-grade yield engine – custody intact, risk isolated, execution spanning both DeFi and CEXes. Where adding protocols don’t require endless code, new adapters, or patching dashboards. That’s Core Vaults by Mellow. And they’re live today.

Your deposits are protected before they're touched. First-loss protection for @LidoFinance's Earn vaults on Mellow. 5M$ of protocol reserves from Lido absorb losses before you do. Skin in the game, onchain.

Future leaders will build their businesses onchain. They need to graduate as Web3 natives. Not just from tech courses, but business and law schools. Today, the DeFi industry calls on US universities to meet this challenge, with our support. Learning brings the world onchain.

DeFi, simplified: Introducing MetaVaults x.com/i/broadcasts/1…

MetaVaults are live on @LidoFinance. Here we'll break down why this matters. Speakers for "DeFi, simplified: Introducing MetaVaults" @etn1337 – Head of Ecosystem, Mellow @defiyaco – Head of ETH Products, Lido Earn March 17th, 16:00 CET. Join the livestream on @mellowprotocol.

What we'll cover: - Why Lido is expanding beyond ETH with EarnUSD. - What "vaults that manage vaults" means in practice. - How curators are selected, how strategies get added, and how the risk model works. Speakers dropping soon.

MetaVaults are live. Now let's talk about what they are and why they really matter. Join us and @LidoFinance for a live session: "DeFi, simplified: Introducing MetaVaults". 30 minutes. No slides. Just a conversation. March 17th, 16:00 CET.

Vaults that manage vaults. Each strategy gets its own curator. The best ones get added over time. The first onchain fund-of-funds infrastructure. That's MetaVaults by @LidoFinance. Powered by Mellow.

You deposit once. The best strategies come to you. EarnETH Lido: stake.lido.fi/earn/eth Mellow: app.mellow.finance/vaults/earn-eth EarnUSD Lido: stake.lido.fi/earn/usd Mellow: app.mellow.finance/vaults/earn-usd Now live on @LidoFinance. Built on Mellow.

DeFi has never had this. Every vault was one strategy, one curator, one bet. If you wanted diversification you had to manage it yourself across ten tabs and five wallets. MetaVaults change that. Think TradFi fund-of-funds, but onchain and fully transparent. For real this time.

What if you didn't have to pick a strategy at all? What if the best ones just showed up in your vault over time, each run by its own curator? That's what @LidoFinance's MetaVaults are. EarnETH and EarnUSD vaults put the best strategies under one roof for you. Built on Mellow.

Bitcoin is shifting from passive storage to programmable capital. Mellow's ecosystem lead @etn1337 is joining @RootstockLabs, @Tyr_Capital, and @utila_io to push that conversation forward on March 26.

Both vaults curated by @sense_capital – same risk philosophy, different execution paths. Mezo rewards on both vaults. Unlock is March 26. Until then, the strategy is in place and capital will deploy as conditions line up. Now your BTC has a job, and it's about to clock.

The cbBTC vault stays on Ethereum entirely. cbBTC pairs against tBTC on @Uniswap v4 – same stable BTC-to-BTC logic, same near-zero impermanent loss. @yieldbasis adds fee capture and gauge rewards on top. No bridging, no MUSD minting. Simpler path, same risk discipline.

Two BTC vaults by @MezoNetwork on Mellow received updates – strategy is live and already generating yield. BTC is now earning on both Ethereum and Mezo, with Mezo rewards stacking on top. Here's how the vaults are set up and what your BTC is actually doing.

[Oracle Incident] Yesterday Aave's CAPO oracle quoted an incorrect wstETH:USD price boundary used within AAVE markets, resulting in liquidations. No bad debt was incurred, and all affected users will be fully reimbursed. These incorrect pricing boundaries have nothing to do with wstETH as an underlying asset and are not related to any issues with wstETH or the Lido protocol. Lido Earn products, including stRATEGY and GGV, are not affected by these liquidations and user funds remain safe. Find the full context from the @chaoslabs team below ↓