Glassnode
Aave V3 lost roughly $4.0 billion in available liquidity inside a 29-hour window after the Kelp DAO rsETH bridge exploit, exposing how a single cross-chain bridge failure can cascade through the largest on-chain lending market.
WETH utilization on the protocol hit 100% in 1.4 hours, seven hours before the Protocol Guardian froze the market — meaning borrowers had unrestricted access to the drained side of the book for almost an entire business day after liquidity had effectively run out.
Why it matters
The contracts held throughout. The bridge did not. Aave's code behaved as designed; the upstream Kelp DAO rsETH bridge failure dragged an external asset onto the protocol's books at a price the oracle had to reconcile, and reconciliation meant withdrawals had to come from somewhere. That somewhere was $4B of usable liquidity evaporating in just over a day. The episode is the cleanest case yet that protocol-level safety on a blue-chip money market is now bounded by the weakest cross-chain bridge it accepts as collateral.
Market impact
The Protocol Guardian's freeze ended the bleeding, but the structural read for the rest of DeFi is sharper than the headline number. Aave V3 has been treated as the safest large-scale on-chain venue for nearly two years; a $4B liquidity drawdown inside 29 hours, with a seven-hour gap between full WETH utilization and the guardian intervention, resets the bar for how markets price bridge-wrapped collateral on lending rails.
Frequently asked questions
-
How much liquidity did Aave V3 lose in the Kelp DAO rsETH exploit?
Aave V3 lost roughly $4.0 billion in available liquidity inside a 29-hour window after the Kelp DAO rsETH bridge exploit rippled through the protocol.
-
How fast did WETH utilization hit 100% on Aave V3?
WETH utilization on Aave V3 hit 100% in 1.4 hours after the exploit began, and stayed there for roughly seven hours before the Protocol Guardian froze the market.
-
What is the Kelp DAO rsETH bridge exploit?
The Kelp DAO rsETH bridge exploit was an upstream cross-chain bridge failure that dragged an external asset onto Aave's books at a price the oracle had to reconcile, triggering a $4B liquidity drawdown.
-
Did Aave's smart contracts fail during the exploit?
No. The contracts held throughout; Aave's code behaved as designed. The failure originated at the Kelp DAO rsETH bridge layer, not inside Aave's lending protocol itself.
-
What is the broader DeFi takeaway from the Aave V3 liquidity loss?
The episode is the clearest case yet that protocol-level safety on a blue-chip money market is now bounded by the weakest cross-chain bridge it accepts as collateral — resetting how the market should price bridge-wrapped assets on lending rails.
TheBlock
CoinTelegraph
Crypto News
WuBlockchain
CoinDesk