Aave Moves to Retire 50 Reserves and Six Deployments

Aave's governance forum took up a proposal on 30 July to deprecate 50 low-adoption reserves and wind down six entire chain deployments, a list covering $98.1 million of supplied assets and $15.6 million of outstanding debt across the lending protocol. The Block, crypto.news and The Crypto Times all carried the filing the same day. Nothing was switched off on submission. The proposal sat at the ARFC stage, an Aave Request for Comment, the discussion step that comes before any vote, with an off-chain Snapshot poll and then a binding on-chain vote still ahead of it. Aave's own framing was that the wind-downs are risk reduction, not a strategic judgment on layer 1 versus layer 2 networks.

What a reserve is and what retiring one does

A reserve in a lending market is a single asset's pool: the place where every deposit of that token sits, where borrowers draw it from, and where its own interest rate, collateral rules and caps are set. A protocol like Aave runs dozens of them side by side on each chain it is deployed to. Each one costs something to keep. There is a price feed to hold accurate, parameters to tune, and a risk surface that has to be watched whether or not anyone is using it. Deprecating a reserve ends its future rather than seizing its present: new supply and new borrowing stop, and existing lenders and borrowers unwind their positions over time. The proposal set no immediate enforcement and explicitly gave users time to exit, which matters when the assets involved are real balances and not abandoned dust. Also on the list were 21 matured Pendle principal tokens, fixed-term instruments already past their maturity date, and 25 reserves that sit on the six chains being closed outright.

Six chains, and why these six

The six full deployments being wound down hold $12.8 million supplied and $4.1 million borrowed between them, a small slice of the total in the proposal. The remaining reserves are spread across 11 other deployments that stay open, and account for $85.3 million supplied and $11.5 million borrowed. The per-chain figures, with deposits measured over the previous six months, show why these six were singled out:

Sonic: $7.6 million supplied, $2.7 million borrowed, deposits down 74%
Scroll: $2.2 million supplied, deposits down 86%
Aptos: $1.7 million supplied, $719,000 borrowed, deposits down 94%
zkSync: $844,000 supplied, deposits down 88%
Metis: $297,000 supplied
Soneium: $173,000 supplied

Why money still sitting there is not enough

Pruning a deployment that holds live deposits looks counterintuitive until the cost side is counted. Every additional chain is another set of oracles to maintain, another bridge to monitor, another environment where an integration bug or a mispriced feed can drain a pool. The security work does not shrink with the balance at stake. That asymmetry has a price on record: a single flawed price oracle on a smaller chain was enough to cost one lending market $9.05 million on 11 July, in a third-party contract the protocol itself did not write. Aave's six exits hold $12.8 million combined and are shrinking at rates between 74% and 94% over six months, a shape that rarely reverses on its own. It also fits a wider pattern of protocols narrowing where they run instead of defending every network they once expanded onto.

Two votes before anything closes

The path from here runs through the Snapshot poll, where token holders signal off-chain and without gas cost, and then to an on-chain vote that actually executes the parameter changes if it passes. Either step can narrow the list. A proposal covering 50 reserves across 17 deployments tends to get argued chain by chain, not accepted whole. What is not yet visible is how quickly the $15.6 million of outstanding debt is repaid once borrowers know their markets are being retired, and whether lenders on the six exiting chains withdraw in an orderly way or all at once. Until the on-chain vote is settled, every reserve on the list keeps operating exactly as it did before.