#JointEscapeHatchforAaveETHLenders *"Joint Escape Hatch" for Aave ETH Lenders – Post Kelp Exploit*
After the April 18 Kelp DAO $292M rsETH exploit, Aave ETH lenders got trapped. Here’s the “escape hatch” situation:
*1. Why ETH lenders needed an escape hatch*
- *The problem*: Attacker dumped 116,500 stolen rsETH on Aave V3, borrowed ∼82,650 WETH + 821 wstETH = $236M
- *Result*: Aave’s WETH pool hit *100% utilization*. At 100%, lenders literally cannot withdraw - there’s no ETH left
- *Scale*: $5.4B+ outflows, TVL dropped $6.28B from $26.39B to $20.11B as whales fled
- *Bad debt*: $177M-$200M estimated. Some sources say $236M
*2. What’s the "Joint Escape Hatch"?*
This refers to coordinated bailout/liquidity measures being worked on by Aave + Kelp to let ETH lenders exit:
*Current status per sources*:
- *Aave + Kelp working independently of LayerZero* on a potential bailout
- *Best case*: Raise ∼110K ETH to fill the gap
- *Reality*: Aave takes a hit either way. 86% of all rsETH was on Aave, so billions would be stuck if L1 affected c164
*Other mechanisms in play*:
1. *Aave Umbrella backstop*: Expected to cover the $177M-$200M bad debt
2. *Arbitrum freeze*: Security Committee froze 30,766 ETH tied to the hacker on Arbitrum One. Those funds could go toward recovery
3. *rsETH markets frozen*: Aave froze rsETH + WETH reserves on Ethereum, Arbitrum, Base, Mantle, Linea to stop more borrowing
*3. Can ETH lenders withdraw now?*
- *Short answer*: Not fully. With 100% utilization, withdrawals are blocked until liquidity returns
- *What’s happening*: Aave DAO service providers are evaluating "bad debt" scenarios and coordinating to close the gap
- *No direct Aave hack*: Protocol itself wasn’t exploited. Issue was external rsETH collateral
*4. What to watch*
1. *Aave governance proposals*: Market freezes, debt management plans
2. *Bailout fundraise*: Whether Aave/Kelp can raise the ∼110K ETH
3. *Frozen hacker funds*: If Arbitrum’s 30,766 ETH gets returned to Aave