Go to app

Scope of Deprecation

Published 7/30/2026, 9:49:29 AM

Aave's deprecation of approximately 75 reserves across 11 deployments—including the complete exit from 6 blockchains—represents a strategic shift toward a Portfolio-Level Risk Framework designed to reduce operational overhead and protocol attack surfaces [Source: https://governance.aave.com/t/arfc-low-adoption-asset-deprecation-on-aave-v3/25401]. By offboarding roughly $98.1 million in supplied assets and $15.6 million in debt, Aave is prioritizing high-liquidity, high-revenue markets over "long-tail" assets that pose disproportionate oracle and liquidation risks [Source: https://www.theblock.co/post/410127/aave-proposes-reserve-deprecations-affecting-98-million-in-supplied-assets].

Scope of Deprecation

The proposal targets low-utilization assets and redundant bridged tokens to streamline the protocol's cross-chain footprint.

CategoryDetailsKey Assets/Chains Affected
Full Chain Exits6 ChainsSonic (S), Scroll (SCR), zkSync (ZK), Metis, Soneium, Aptos (APT)
Asset Offboarding50+ AssetsFBTC ($11.1M), eBTC ($5.3M), CRV ($2.2M), UNI ($1.7M)
Yield Tokens21 AssetsMatured Pendle Principal Tokens (PTs)
Legacy TokensBridged DuplicatesWBTC.e and LINK.e on Avalanche (favoring native versions)

[Source: https://governance.aave.com/t/arfc-low-adoption-asset-deprecation-on-aave-v3/25401]

Reshaping the Risk Profile

This move is a proactive response to the $292 million KelpDAO rsETH exploit in April 2026, shifting Aave from reactive parameter adjustments to a systematic reduction of protocol complexity [Source: https://thedefiant.io/news/defi/aave-proposes-protocol-wide-risk-framework-after-kelpdao-exploit].

  • Oracle Risk Reduction: By removing assets with thin liquidity, Aave reduces its reliance on external price feeds that are vulnerable to manipulation.
  • Liquidation Efficiency: The protocol focuses on assets with deep on-chain liquidity, ensuring that liquidations can be executed during market volatility without incurring significant bad debt.
  • Operational Efficiency: Exiting underperforming chains like Sonic and Metis allows governance and developers to focus resources on deployments where revenue exceeds the cost of security monitoring and oracle maintenance [Source: https://governance.aave.com/t/arfc-low-adoption-asset-deprecation-on-aave-v3/25401].

Impact on Users and Liquidity

To facilitate these exits, Aave has implemented aggressive economic incentives to "force" user migrations.

Conclusion

Aave's deprecation strategy marks a transition toward a leaner, more resilient protocol. While it results in a temporary reduction in TVL and requires active management from users in affected markets, it significantly lowers the probability of systemic failure by eliminating "ghost" markets and high-risk oracle dependencies. The protocol's risk profile is now more heavily weighted toward battle-tested, native assets on high-volume chains.