Aave Advances Plan to Wind Down 50 Low-Adoption Reserves and Six Markets
Aave governance is advancing a staged plan for 50 low-adoption reserves and six market deployments, alongside a companion proposal for selected long-tail oracle feeds. The package was still moving through governance and implementation as of September 7, 2026.
THE SHORT VERSION
Aave is advancing a governance and implementation plan to wind down low-adoption lending markets and selected long-tail oracle dependencies. The work is being discussed as two related Aave governance ARFCs, one focused on asset and market deprecation and one focused on oracle deprecation. The full package was not confirmed as executed by September 7, 2026. [3] [4]
The practical goal is to reduce maintenance work and operational exposure around markets with limited use. The proposals describe staged controls, migration planning, and governance steps. They do not establish that Aave is abandoning the underlying chains, and they are not evidence of an oracle failure or exploit.
WHAT THE LOW-ADOPTION PROPOSAL COVERS
LlamaRisk opened the two ARFCs on July 29, 2026. Active proposal discussions were visible on August 13. The Aave V3 low-adoption proposal covers 50 reserves and 21 matured Pendle principal tokens across 11 deployments. Its proposal snapshot reported about $85.3 million supplied and $11.5 million in debt. Those are proposal-era figures, not live balances for September 7. [3] [5]
The same proposal also covers six low-adoption market deployments: Sonic, Scroll, zkSync, Metis, Soneium, and Aptos. The snapshot reported about $12.8 million supplied and $4.1 million in debt across those markets. The numbers help explain the scope under discussion, but they do not predict how much liquidity or debt remains while governance and implementation work continue. [3] [6]
Aave Labs’ development update posted September 1 said low-adoption deprecation had moved into implementation, with an AIP being prepared. LlamaRisk’s August monthly update, posted September 4, restated the proposed scope and mechanics. These updates show an active process, not proof that every reserve, asset, or chain-specific market has already been shut down. [1] [2]
HOW THE STAGED WIND-DOWN WORKS
The proposed wind-down uses controls that can restrict new activity before a market is fully removed. The described measures include freezing selected reserves and reducing supply and borrow caps to 1. In plain terms, those settings can stop normal growth while giving users a defined path to reduce positions. This is different from claiming that all positions would be abruptly liquidated.
The final parameters, reserve list, user exit windows, execution order, and AIP payloads were not settled in the materials reviewed for this draft. A market can also have different technical constraints from another market. Readers should therefore treat the proposal as a framework under governance review, not as a single completed transaction or a universal timetable.
THE ORACLE-DEPRECATION COMPANION
The companion ARFC covers selected long-tail assets across Aave V2 and V3. LlamaRisk describes operational risk related to low adoption and illiquidity, then proposes asset-specific migration plans using fixed-price adapters and controlled parameters. The purpose is to manage how pricing dependencies are retired or migrated when a feed has limited practical use.
That proposal should not be read as evidence that an oracle failed, that an exploit occurred, or that every asset covered by the discussion is unsafe. An oracle deprecation plan is an operations and risk-management decision. The relevant question is how each asset’s price source, parameters, and user exit process would be handled in the final implementation. [4]
WHAT IS CONFIRMED, AND WHAT IS NOT
Confirmed materials establish an active governance and implementation process. They establish the proposal-era counts and balances, the six named market deployments, the staged-control approach, and the companion discussion about long-tail oracle feeds. They also establish that Aave Labs was preparing an AIP while LlamaRisk continued to document the work. [1] [2] [3] [4]
They do not yet confirm the final AIP or payloads, the final reserve list, individual market parameters, user exit windows, execution order, or dates for every action. Those details may change through governance. This article does not infer a judgment about the technology of Sonic, Scroll, zkSync, Metis, Soneium, or Aptos from a proposed market wind-down.
WHAT READERS SHOULD WATCH NEXT
Watch the Aave governance forum for the final AIP, its payloads, and any updated reserve or market list. Compare the final parameters with the ARFC descriptions, especially freeze settings, caps, migration steps, and user communications. Also watch for implementation transactions and official status updates that distinguish an approved proposal from an executed change. Until those records are available, the careful description is that Aave is advancing a staged wind-down plan and an oracle-deprecation companion proposal.
SOURCES AND DISCLOSURES
[1] Aave Labs development update, August 2026, posted September 1:
https://governance.aave.com/t/al-development-update-august-2026/25579
[2] LlamaRisk monthly community update, August 2026, posted September 4:
https://governance.aave.com/t/llamarisk-monthly-community-update/17935/32#p-65334-research-and-analysis-8
[3] LlamaRisk ARFC, “Low Adoption Asset Deprecation on Aave V3”:
https://governance.aave.com/t/arfc-low-adoption-asset-deprecation-on-aave-v3/25401
[4] LlamaRisk ARFC, “Oracle Deprecation for Long-Tail Assets Across Aave V2 and V3”:
https://governance.aave.com/t/arfc-oracle-deprecation-for-long-tail-assets-across-aave-v2-and-v3/25400
[5] Aave governance Snapshot proposal for the low-adoption V3 plan:
https://snapshot.box/#/s:aavedao.eth/proposal/0x4ec0c13baf55472ecd538a2fae4bbdb60f30c96621a97ecf4db073b3e65597c7
[6] Aave governance Snapshot proposal for the companion oracle plan:
https://snapshot.box/#/s:aavedao.eth/proposal/0xaa683250ff2e2835b9ac945d6219a35cdca1d4134f49e3bce6763ca8d8944c08
Disclosure: This is an editorial report on public governance materials, not financial advice and not a recommendation to lend, borrow, buy, sell, or hold any asset. Proposal-era figures are not live balance data, and governance or implementation details may change. The featured illustration was generated for CryptoWorkPro and is not a documentary image of an Aave market, oracle, or governance event.