Executive Summary
Aave has formally asked Arbitrum to unfreeze roughly $73 million worth of ETH that has been held in escrow since the Kelp DAO hack. The frozen ether is intended to re‑establish the backing of rsETH, Aave’s liquid‑staking token, and to reassure users that the product remains fully collateralised. While Arbitrum possesses the technical means to release the assets, it has not yet acted on Aave’s request.
What Happened
Earlier this week, Aave submitted a request to the Arbitrum governance framework, urging the L2 chain to release the locked ETH. The amount in question, about $73 million, was frozen as part of the remediation effort following the Kelp DAO hack. Aave argues that unlocking the ether is essential for restoring the full backing of rsETH, which relies on a one‑to‑one relationship with staked ETH.
Arbitrum’s technical team confirmed that it can execute the release, but no transaction has been initiated. The delay has prompted Aave to publicly highlight the issue, framing it as a matter of user protection and ecosystem stability.
Background / Context
The Kelp DAO hack, which resulted in an estimated loss of $292 million in crypto assets, forced several protocols to freeze assets tied to the compromised smart contracts. Among those assets was a pool of ETH earmarked to back rsETH, Aave’s liquid‑staking derivative that allows users to earn staking rewards without locking up their ETH directly.
rsETH operates by holding staked ETH in a custodial contract and issuing a token that mirrors the value of the underlying stake. When the Kelp DAO incident occurred, the associated ETH was placed in escrow to prevent further exposure and to safeguard the token’s peg. Aave’s request therefore targets the restoration of that peg, which is critical for users who depend on rsETH for yield generation and liquidity.
Reactions
Aave’s leadership has emphasized that the frozen ETH represents a liability that must be addressed to maintain confidence in its staking products. In a statement, Aave noted that unlocking the assets would “protect users of rsETH and uphold the integrity of the broader DeFi ecosystem.”
Arbitrum’s response has been more measured. While acknowledging the technical feasibility of releasing the funds, the platform has not provided a concrete timeline for action. Community members on both protocols’ forums have expressed concern that prolonged inaction could erode trust, especially among liquidity providers who rely on the certainty of token backing.
What It Means
If Arbitrum proceeds with the release, rsETH’s collateralisation would be restored, reinforcing user confidence in Aave’s liquid‑staking offering. This could encourage continued inflows into rsETH and stabilize the token’s market perception, which has been under pressure since the hack.
Conversely, continued delay may prompt users to withdraw from rsETH or seek alternative staking solutions, potentially reducing Aave’s staking‑related revenue. The incident also highlights the interdependence of L2 solutions and DeFi protocols, underscoring the need for clearer coordination mechanisms when emergency freezes occur.
What Happens Next
Aave has indicated that it will monitor Arbitrum’s actions closely and may explore additional governance measures if the release does not occur promptly. Arbitrum, for its part, is expected to discuss the request in its upcoming governance vote, where token holders will decide whether to authorize the transaction.
Stakeholders across the ecosystem are watching the outcome as a litmus test for how quickly decentralized platforms can respond to security incidents. The resolution will likely shape future protocols for emergency asset freezes and the collaborative processes needed to unwind them.