Aave governance has proposed a sweeping reserve deprecation package that would offboard dozens of low-adoption assets and fully wind down six chain deployments, affecting $98.1 million in supplied assets and $15.6 million in outstanding debt.
The proposal covers 50 low-adoption reserves and 21 matured Pendle PT (Pendle Principal Token) positions. It also retires the Aave deployments on Sonic, Scroll, zkSync, Metis, Soneium and Aptos entirely. Affected users would need to repay or migrate positions before the offboarding executes.
Why it matters
The move is a cleanup signal rather than a stress event. Aave has accumulated tail reserves across a multi-chain expansion that, individually, carry little liquidity and elevated risk. Bundling the retirements into a single governance vote is cheaper and faster than the protocol's historical one-reserve-at-a-time cadence. For governance watchers, the headline is the breadth: Aave is choosing to shrink where adoption didn't show up, not patch over it.
Market impact
The $98M in supplied assets is a fraction of Aave's $20B+ TVL (total value locked), so the protocol-level market reaction should be muted. The real read is competitive: Aave is concentrating engineering and risk resources on its core Ethereum and high-TVL deployments rather than subsidising long-tail chains that haven't earned the liquidity. The package also clears out the residual risk of matured Pendle PT positions, a category that has generated recurring governance friction since the tokens began expiring.
Frequently asked questions
-
Which Aave deployments are being wound down?
The proposal calls for full wind-downs of Aave's deployments on Sonic, Scroll, zkSync, Metis, Soneium, and Aptos, along with the offboarding of 50 low-adoption reserves and 21 matured Pendle PT positions.
-
How much user capital is affected by the Aave reserve deprecation proposal?
The proposal affects $98.1 million in supplied assets across the targeted reserves and $15.6 million in outstanding debt across the six chain deployments being retired.
-
Is the Aave wind-down a sign of protocol stress?
No. The $98M affected is a small fraction of Aave's $20B+ TVL. The move is a governance-driven cleanup of long-tail reserves that never attracted meaningful liquidity, not a response to insolvency or exploit risk.
-
What should users on the affected Aave chains do?
Users with positions on Sonic, Scroll, zkSync, Metis, Soneium, or Aptos, or in any of the 50 low-adoption reserves, will need to repay or migrate their positions before the offboarding executes once the proposal passes.
-
Why is Aave cutting so many deployments at once?
Aave is concentrating engineering and risk resources on its core Ethereum mainnet and high-TVL deployments rather than maintaining long-tail chain deployments that never earned meaningful liquidity. The bundled approach is faster and cheaper than Aave's historical one-reserve-at-a-time cadence.
TheBlock