#AaveLaunchesrsETHRecoveryPlan

#AaveLaunchesrsETHRecoveryPlan
In a significant move to restore confidence and stability within the decentralized finance (DeFi) ecosystem, Aave, one of the leading lending protocols, has officially launched a comprehensive recovery plan for rsETH. This asset, a liquid restaking token from Kelp DAO, experienced critical volatility and oracle-related issues that threatened user funds and the overall health of Aave’s markets. The recovery plan, developed through extensive community governance discussions, aims to mitigate losses, prevent systemic risk, and reestablish normal operations. Below is a detailed, link-free breakdown of what happened, why recovery was necessary, and how the plan works.

Understanding rsETH and Its Role on Aave

rsETH is a liquid restaking token that represents staked ETH through EigenLayer’s restaking mechanism. It allows users to earn yield from both Ethereum staking and actively validated services (AVS) while maintaining liquidity. On Aave, rsETH was listed as a collateral asset, enabling users to deposit rsETH and borrow other assets against it. This integration provided utility for rsETH holders and deepened liquidity for Kelp DAO.

However, the complexity of restaking tokens introduces unique risks, particularly around price oracles. Unlike simple ERC-20 tokens pegged to ETH, rsETH’s value derives from multiple underlying yield sources and can deviate from the expected exchange rate under extreme market conditions or oracle malfunctions.

The Incident That Triggered the Recovery Plan

In late March 2024, a sudden and severe price feed anomaly occurred for rsETH on certain decentralized oracle networks. Specifically, the reported price of rsETH dropped significantly—by over 50% in a matter of blocks—while the actual market value remained stable. This incorrect price was consumed by Aave’s price oracle adapter, leading to a cascade of liquidations.

Borrowers who had posted rsETH as collateral suddenly saw their health factors drop to dangerous levels. Many positions were liquidated automatically, and liquidators seized the discounted rsETH collateral. However, because the liquidation was based on a false price, users lost far more value than they should have. Some rsETH collateral was sold off at artificially low prices, creating a bad debt situation for the protocol.

After the incident was detected, Aave’s risk management team paused rsETH borrowing and liquidations, but the damage had already been done. The protocol faced a deficit—unbacked liabilities—that needed to be addressed to protect remaining lenders and depositors.

Key Components of the Recovery Plan

The Aave community, through the Aave Governance system, voted on and approved a multi-phase recovery plan. The plan is designed to be fair to affected users, protect the protocol’s solvency, and prevent recurrence. Here are its main elements:

1. Immediate Suspension and Parameter Changes

Before any recovery could begin, Aave’s emergency administrators (part of the Aave Guardian system) disabled rsETH as collateral and paused all new deposits and borrows involving the token. The liquidation threshold was temporarily set to zero to prevent further automated liquidations. Existing positions were frozen but not closed, giving users time to react without forced liquidations.

These parameter tweaks were essential to stabilize the market and stop the bleeding. Borrowers could still repay their loans or withdraw their collateral, but no new risk was introduced.

2. Bad Debt Coverage via Aave’s Safety Module

Aave has a Safety Module (SM) that holds staked Aave tokens (stkAAVE) and stkABPT (Balancer pool tokens). This module acts as a backstop: in the event of a shortfall, the SM can be used to cover bad debt. The recovery plan included a proposal to utilize a portion of the Safety Module’s funds to absorb the deficit caused by the rsETH oracle attack.

The amount of bad debt was calculated to be approximately 1.6 million USD-equivalent. The SM covers this by minting and selling AAVE tokens or directly writing down liabilities. This step ensures that lenders on Aave’s rsETH market—who supplied assets expecting to be repaid—do not suffer losses.

3. Affected User Compensation Mechanism

One of the most debated parts of the plan was how to compensate users who were unfairly liquidated. The governance discussion concluded that while liquidations are a risk of borrowing, those triggered by a false oracle price constitute an extraordinary event. Therefore, the recovery plan includes a retrospective claims process.

Users who can prove that their positions were liquidated between specific block timestamps when the erroneous price was active may receive partial or full compensation. The compensation comes from a combination of:

· A portion of the recovered funds from the liquidation auction (some liquidators returned profits voluntarily)
· An allocation from the Aave treasury’s ecosystem reserve
· A separate distribution from Kelp DAO, which acknowledged the oracle issue and contributed to the fund

The exact compensation formulas are based on the difference between the false liquidation price and the true market price at the same moment, multiplied by the amount of rsETH collateral lost.

4. Oracle Redundancy and Circuit Breakers

To prevent a similar event in the future, Aave is implementing new oracle safeguards for all restaking tokens and other volatile assets. The recovery plan mandates the following technical upgrades:

· Multi-oracle aggregation: Price feeds will be sourced from at least three independent oracle providers (e.g., Chainlink, Chronicle, RedStone). Aave’s L2 price adapter will compare them and use the median, rejecting outliers.
· Circuit breakers: If the reported price of an asset changes by more than a configurable percentage (e.g., 10%) within a single block or over short time window, the protocol will automatically pause that market’s liquidation and borrowing functions. The pause must be manually lifted by Aave Guardians after verification.
· Grace periods for liquidations: When an asset’s price drops sharply, liquidations will be delayed by a few seconds or one block to allow arbitrageurs and oracles to correct any temporary discrepancy.

These changes are currently being audited and will be deployed via an Aave Improvement Proposal (AIP) across all networks where rsETH is listed.

Timeline of the Rollout

The recovery plan is being executed in phases over approximately four to six weeks. The initial freeze on rsETH markets lasted 72 hours, after which the Safety Module activation began. The claims portal for affected users opened on day five and will remain active for 90 days. Oracle upgrades are slated for completion within two months, pending audits. Full resumption of rsETH as collateral (with new safeguards) is expected only after all technical improvements are live and community confidence is restored.

Community and Market Reactions

Early reactions from the Aave and wider DeFi community have been cautiously positive. Many praised the swift governance action—the first emergency proposal was submitted within four hours of the oracle anomaly. The decision to tap the Safety Module rather than socialize losses among all protocol users was widely seen as the correct use of the insurance-like fund.

However, some critics argue that the compensation process for liquidated users remains too complex and may exclude retail borrowers who lack the technical ability to provide proof of liquidation events. Others worry about the precedent this sets: will Aave bail out users for any oracle failure in the future? Governance delegates have clarified that this is a one-time exception due to the extreme nature of the price deviation (over 50% in seconds) and that standard liquidation risk remains with the borrower.

Lessons for the DeFi Ecosystem

The rsETH incident and Aave’s recovery plan highlight several key lessons. First, liquid staking and restaking tokens introduce novel risk dimensions, including complex price discovery and multiple layers of oracles. Second, even battle-tested protocols like Aave can suffer from unexpected oracle failures. Third, decentralized governance can act quickly when emergency mechanisms and clear communication channels exist.

For users, this event reinforces the importance of monitoring position health factors—even when relying on “safe” collateral. For protocol developers, it underscores the need for fallback oracles, time-weighted average prices (TWAPs) for certain assets, and better simulation of extreme market conditions.

What Happens Next

As of the latest updates, the rsETH market on Aave remains in a recovery state. Borrowers with open positions can still repay their debts to withdraw their remaining collateral. The bad debt covered by the Safety Module has been settled, and treasury funds are being distributed to eligible claimants. The new oracle system is undergoing testing on Aave’s testnet, with a governance vote scheduled for the final deployment.

Aave is also working with Kelp DAO to improve rsETH’s own oracle committees and provide real-time health dashboards. Once all upgrades are in place, the community will consider a proposal to re-enable rsETH as collateral with stricter risk parameters—likely a lower loan-to-value (LTV) ratio and a higher liquidation threshold.

The recovery plan for rsETH demonstrates that DeFi is maturing. While incidents like these test the resilience of the ecosystem, the existence of structured, transparent, and community-driven recovery processes turns crises into opportunities for improvement. Aave’s handling of this event may become a blueprint for how lending protocols address oracle-related failures in the future, balancing user protection with protocol solvency. For now, the message is clear: DeFi continues to evolve, one challenge at a time.