Aave is weighing a broad cleanup of its V3 deployments, with a new proposal recommending the protocol wind down markets on six blockchains and offboard 50 low-use reserves spread across 11 deployments. The plan, dated July 28, 2026, comes from DeFi risk management service provider LlamaRisk, working alongside other Aave service providers.
The chains under review are Sonic, Scroll, zkSync, Metis, Soneium, and Aptos. Together they account for 25 reserves holding roughly $98.1 million in supplied assets and $15.6 million in outstanding debt — a small fraction of Aave's overall footprint, but enough activity that an orderly wind-down rather than an abrupt freeze is being proposed.
Most of the Work Is Already Done
In practice, much of the proposal simply ratifies decisions already in motion. Reserves on Scroll, zkSync, Metis, and Soneium have already been frozen, meaning no new deposits or borrows can be opened against them. Sonic and Aptos remain fully active for now, and the proposal recommends freezing both as the next step toward a full offboarding.
Alongside the chain-level cuts, LlamaRisk is also recommending the retirement of 21 matured Pendle principal token listings, instruments that have already reached expiry and no longer serve an active purpose on the protocol.
Why Aptos Is on the List
The case against keeping Aptos active is laid out in blunt numbers. Aave launched on the network 11 months ago, but LlamaRisk's data shows available liquidity has fallen 94% over the past six months, while the deployment's quarterly revenue has dropped below $1,000 — a level that no longer justifies the ongoing technical and security overhead of maintaining the market.
Part of a Broader Risk Framework
Aave founder Stani Kulechov framed the proposal as part of a deliberate strategy shift rather than a one-off cleanup. According to Kulechov, the goal is to "reduce Aave's economic and technical risk surface as part of the new Aave Risk Framework."
That framework appears aimed at concentrating liquidity and engineering attention on Aave's highest-usage markets rather than maintaining a long tail of deployments with thin activity, each of which still carries its own attack surface, oracle dependencies, and monitoring burden regardless of how little capital sits inside it.
If adopted, the proposal would mark one of the more significant consolidations of Aave's multi-chain footprint since the protocol began expanding aggressively across layer-2s and alternative chains in prior years.
