Aave DAO has initiated a governance proposal to deprecate 75 isolated reserves and six associated deployments across its lending protocol. The move directly affects $98.1 million in supplied assets and $15.6 million in outstanding debt, with the stated goal of consolidating liquidity and reducing operational complexity.
The proposal, submitted by the Aave Risk DAO, identifies the targeted reserves as having consistently low utilization and minimal trading activity. Maintaining these illiquid markets incurs unnecessary oracle costs and monitoring overhead. Most of the targeted assets are long-tail tokens with dwindling on-chain liquidity.
The deprecation process runs in two phases. First, reserves will be frozen, blocking new deposits and borrowing. Second, a subsequent governance vote will delist the assets entirely. Users holding positions in affected reserves will need to migrate their capital.
Suppliers in the affected reserves will no longer earn interest or use those assets as collateral once frozen. Borrowers retain their debt but face pressure to repay or refinance before full delisting. The proposal includes a transition period to minimize disruption.
The $98.1 million represents less than 1.5 percent of Aave's total supplied capital. Aave V3, the protocol's primary deployment, currently holds over $7.5 billion in TVL across multiple chains.
The 75 reserves span several deployments, including legacy Aave V2 instances on Ethereum and Polygon. Specific assets include RUNE, DPI and older stablecoin variants—markets that have seen no material activity for several quarters.
Liquidity providers in deprecated pools will need to withdraw their funds, potentially routing stablecoins and other assets back into more active Aave markets or broader circulation.
The proposal is currently in the snapshot phase, allowing AAVE token holders to signal support. If it passes, it proceeds to an on-chain vote requiring a majority of staked AAVE for execution.
The primary risk is liquidation exposure for borrowers who fail to repay before full delisting. Sudden volatility in affected long-tail assets could accelerate that risk, though Aave's existing risk parameters are designed to manage orderly wind-downs.
Removing underutilized reserves shrinks the protocol's attack surface and frees resources for core development and risk management on higher-demand markets. Compound and MakerDAO have run similar reserve-pruning processes as their protocols matured.
Users should monitor the Aave governance forum for voting timeline updates and migration instructions. The Aave frontend will display warnings for affected positions ahead of any final delisting.
