On the Day Aave Launched rsETH, Spark Strategically Exited

Key Takeaways:

• Aave enabled rsETH lending at a 93% LTV, while Spark withdrew due to low utilization by January 2026.
• The Kelp DAO cross-chain bridge attack led to 116,500 unbacked rsETH; Aave now faces $195 million potential bad debt.
• Spark’s foresight in risk management avoided losses, relying on governance decisions, not anticipating vulnerabilities.
• Aave’s current insurance covers 25% of the debt, showing operational risks in its expansion strategy.
• Spark’s risk mitigation strategies highlight the benefits of exit mechanisms like rate limits and diversified oracles.

WEEX Crypto News, 2026-04-21 15:25:08

Aave’s Expansion: A Risk That Backfired

On April 18, the crypto world was shaken when Kelp DAO’s cross-chain bridge was exploited, creating 116,500 rsETH tokens without backing. Aave, which recently introduced rsETH-enabled borrowing with a maximum 93% Loan-to-Value (LTV) ratio, quickly froze this asset, yet the damage was done with $195 million potential bad debt reported by Lookonchain analysts. This high exposure underlines a critical flaw in Aave’s aggressive market expansion which relied on a proposal from November 2025 by ACI, targeting a $1 billion rsETH inflow.

Spark’s Strategic Withdrawal Reflects Prudent Risk Management

Meanwhile, SparkLend, operating under the MakerDAO umbrella, faced no such losses. The decision behind their strategic rsETH withdrawal, finalized on January 29, 2026, was well documented three months prior in a governance post. PhoenixLabs, the driving force behind Spark’s ecosystem, identified low utilization rates and concentration risks as key factors for divestment from rsETH markets.

Decision Divergence: Spark Exits, Aave Expands Driven by Governance

The strategic divergence between Aave and Spark encapsulated different operational philosophies. Spark’s action was not reactionary to the bridge’s security issues but rather an exercise in proactive asset management, reducing reliance on lightly used assets like rsETH which saw negligible adoption except for a single wallet (0xb99a). This logic supported a timely divestment, reinforcing safety and returns while maintaining operations on robust assets.

Aave’s Operational Consequences and Financial Fallout

Aave’s reliance on swift expansion coupled with many governing bodies’ approval, such as Chaos Labs and LlamaRisk, left it vulnerable. Under the pressure of the attack aftermath, Aave’s insurance, worth $50 million, can only cover 25% of potential losses. A broader emergency response was triggered, with aWETH stakers absorbing the initial blow followed by WETH depositors and the DAO treasury.

Spark’s Holistic Defense Apparatus Strengthens Its Position

Spark’s defense system was underscored by its sophisticated precautionary measures. Limits on deposit and borrowing were strategically placed, inhibiting any significant loss exposure in cases of drastic asset influx. In addition, its oracle system depended on a tri-partite median setup, ensuring reliability against price manipulation, distinctly setting it apart from the oracle lag that plagued Aave during the events.

Kelp DAO’s Loss Allocation and Protocols’ Future Path

The path to rectification hinges on Kelp DAO’s final loss allocation decision, with considerations for equitable loss across all rsETH holders or retaining losses on L2 holdings. Regardless of these outcomes, the clear variance in financial repercussions between Aave and Spark highlights the importance of strategic asset evaluations, proving a nimble risk management strategy can shield platforms from severe market disruptions.

Frequently Asked Questions

Why did Aave face significant losses after the Kelp DAO incident?

Aave’s aggressive rsETH expansion, driven by the goal to boost WETH utilization, exposed it to unbacked rsETH tokens due to a cross-chain bridge attack, which led to the threat of $195 million in bad debt.

What was Spark’s rationale for withdrawing from rsETH?

SparkLend opted out of rsETH due to low usage and concentration risk spotted in governance reviews, aligning with prudent risk management practices apart from security concerns.

How does Spark manage risk differently from Aave?

Spark employs stringent exit strategies based on asset utilization and concentration metrics and utilizes capped rates and a diversified oracle system to limit risk exposure effectively.

What are the potential remediation strategies for the losses incurred by Kelp DAO?

The remediation could include socializing losses among all on-chain rsETH holders, isolating losses to L2, or attempting a complex snapshot rollback, all pending Kelp DAO’s decision.

How did Aave’s insurance coverage respond to the incident?

Aave’s umbrellas insurance, insufficient at $50 million, exposed the protocol’s significant financial risk, covering only a fraction of the faced bad debt—demonstrating a need for reevaluation of its risk management framework.