Aave Confirms Suspension of rsETH Reserve Operations on Multiple Networks Including Ethereum Mainnet in Latest Update
In response to the KelpDAO rsETH cross-chain bridge attack, Aave confirmed in its latest update that it has suspended reserve operations related to rsETH on multiple networks including Ethereum Core, Arbitrum, Base, Mantle, and Linea. New deposits and borrowings have been frozen, and the loan-to-value ratio for this asset has been set to 0, while existing positions can still be repaid and liquidated. The protocol stated that this decision aims to allow time and operational space for subsequent fund recovery and bad debt disposal plans, with the goal of recovering as many assets as possible during the recovery process and preventing risks from spreading to other collateral assets and stablecoin pools.
The incident originated from the exploitation of KelpDAO's rsETH cross-chain routing based on LayerZero, where the attacker forged cross-chain messages to withdraw approximately 116,500 rsETH (about 18% of the total supply, valued at nearly $300 million) from the Ethereum side adapter, while the source chain did not correspondingly destroy the tokens. This led to a large amount of "unbacked" rsETH appearing across multiple chains, which was used extensively as collateral in Aave, exposing Aave V3 to potential bad debt ranging from $120 million to $230 million across multiple chains. Aave emphasized in its governance forum report that the risk originated from rsETH and its bridging mechanism, not from vulnerabilities in Aave's own contracts. The protocol service provider is collaborating with KelpDAO, LayerZero, and related public chain teams to assess recovery paths and plans for sharing losses among various funding pools (including security modules and partner treasuries).
Source: Public Information
ABAB AI Insight
Aave's extensive suspension of rsETH reserves appears to be a technical operation on the surface, but it is essentially gaining negotiation leverage and time regarding "who will bear the systemic risk brought by the bridge." The rsETH incident exposes the typical "cross-chain note risk": users believe they hold "re-staked tokens with real collateral support," but once the bridge is compromised, a batch of tokens that are essentially "unbacked shadow notes" appears on-chain, used as high-quality collateral in lending protocols, instantly transmitting bad debt risk from the application edge to the core credit layer. By freezing rsETH and part of the WETH reserves, Aave effectively cuts off the transmission chain, locking losses in the local market and preserving negotiation space for future "who will pay to fill the hole."
This incident again highlights that in the combination of re-staking and cross-chain, the question of "what the asset is" is not determined by the token name, but by the security of the weakest link: here, it is the KelpDAO bridge adapter based on LayerZero, not the staking contract of the Ethereum main chain. When the bridge's validation logic allows the release of target chain tokens without destroying source chain assets, the entire system's "credibility" is reduced to the bridge layer. Once an incident occurs, upstream staking, downstream lending, and further downstream leverage and combination strategies will be forced to recalculate around this batch of "pseudo-assets." For lending protocols, this means that in the future, for any LRT or LST-type assets, it is necessary to not only consider on-chain prices and liquidity but also include "the bridge's security model and recourse" in risk assessments.
Aave's choice to emphasize "the protocol's own contract security, with issues arising from underlying assets" is logically valid, but in financial structure, the outcome will not change due to responsibility allocation: bad debts must be absorbed by someone. Current governance discussions have already proposed that losses be shared by Aave's security module, KelpDAO, related public chain treasuries, and even external insurance/reinsurance funds, which is essentially a practical exercise for a "DeFi version of deposit insurance and liquidation mechanisms." Who is willing and able to pay to fill the gaps caused by cross-chain and re-staking will influence the future credit hierarchy between protocols: protocols and assets willing to absorb user losses will receive a higher "safety premium" in the next round of risk repricing, while those that do not will be labeled as "high yield, high risk" in the long term.
In the longer term, such incidents will accelerate the overall discount of DeFi on the combination of "multi-layer leverage + cross-chain bridges + re-staking." Over the past two years, the industry has layered multiple contracts and bridging risks while chasing yields, but pricing and risk models have mostly still been priced as "single-layer assets"; the rsETH incident, as a nearly $300 million explosion point, will force risk management to shift from "each protocol looking at itself" to "looking at the entire path from the asset perspective": staking sources, public chain layer security, bridging mechanisms, re-staking designs, and lending collateral parameters are all indispensable. For foundational lending protocols like Aave, pausing rsETH is just the first step; more importantly, it is necessary to rewrite the entire "acceptable collateral" layered logic before recovery—future blue-chip collateral asset lists will likely lower the risk weight of cross-chain and multi-layer re-staking assets overall, marking a necessary structural adjustment for DeFi from "chasing yields" to "preserving continuity."