Aave governance is evaluating one of the protocol’s broadest portfolio cleanups to date. The proposal would deprecate dozens of low-adoption reserves and wind down six entire deployments, affecting approximately $98.1 million in supplied assets and $15.6 million in outstanding debt. The proposed Aave chain exits are meant to reduce risk and operating complexity rather than respond to a single new exploit.
The plan covers full wind-downs on Sonic, Scroll, zkSync, Metis, Soneium and Aptos. It also targets individual reserves across a wider group of Aave V3 markets, including mature principal tokens and assets whose usage no longer justifies continued support.
For users, “deprecation” does not mean balances disappear or that positions are instantly liquidated. It describes a staged process that restricts new activity and encourages existing positions to unwind.
What the Aave Chain Exits Include
The complete proposal spans 50 low-adoption reserves and 21 matured Pendle principal-token markets across 11 Aave V3 deployments. Within that total, the six full market exits cover 25 reserves.
The individual reserve removals account for roughly $85.3 million in supplied assets and $11.5 million in debt. The six deployment wind-downs account for about $12.8 million supplied and $4.1 million borrowed. Those figures explain why the initiative can be economically meaningful without threatening the protocol’s largest markets.
The proposal is still a governance process, not a completed action. Discussion, revisions and formal votes can change the scope or timing before parameters are executed onchain.
Why the scope is wider than six networks
Aave’s multichain expansion produced markets with very different levels of activity. Some deployments attracted deep liquidity and consistent borrowing. Others remained small while still requiring oracle monitoring, parameter updates, risk reviews, governance work, audits and infrastructure support.
At the reserve level, a listed asset can also outlive its original use. Pendle principal tokens mature by design, while other collateral or borrowable assets may lose liquidity or demand. Leaving inactive markets open indefinitely adds surface area without necessarily serving users.
The cleanup combines these two issues: retiring specific assets where a market remains viable, and closing whole deployments where the operating case is weak.
How a Gradual DeFi Wind-Down Works
The first step is generally to prevent new exposure. Reserves can be frozen, and supply or borrow caps can be reduced to a nominal level. Existing users can repay, withdraw or otherwise close positions, but the market stops accepting meaningful new deposits and debt.
The proposal also contemplates raising reserve factors. A higher reserve factor sends a larger share of borrower interest to the protocol, reducing the return available to suppliers and encouraging capital to move elsewhere. For whole-market retirements, the factor could move to 99%, paired with higher base borrowing rates later in the process.
These levers create incentives for voluntary migration. They are less abrupt than immediately disabling withdrawals or forcing every borrower to close on the same day.
Position holders still need to act
Gradual does not mean passive users can ignore the process forever. Borrowers should monitor rate changes, collateral factors and liquidation thresholds. Suppliers should check whether available liquidity is sufficient for withdrawal, particularly in smaller markets where many users may exit at once.
Integrators also need to update interfaces and routing logic. A front end, aggregator or automated strategy that continues directing funds toward a frozen deployment can create a poor user experience even if the underlying contracts remain accessible.
The governance forum and onchain proposal payloads are the authoritative places to verify final parameters. Social summaries can highlight the direction, but they may not capture every affected reserve.
Why Aave Is Prioritizing Risk Efficiency
The proposal follows a wider effort to formalize how Aave evaluates assets and deployments throughout their life cycles. Recent stress around bridged and restaked collateral reinforced a simple lesson: every supported asset brings dependencies that can change after listing.
Risk is not limited to the smart contract Aave controls. It can enter through a bridge, issuer, oracle, redemption mechanism or thin secondary market. Smaller deployments may also depend on local infrastructure with less redundancy.
Continuous review is therefore as important as initial onboarding. A reserve that once met liquidity and oracle standards may cease to do so, while a chain that once promised growth may no longer generate enough activity to cover the attention it requires.
Efficiency is not the same as centralization
Reducing the number of deployments can look contrary to a multichain strategy, but breadth is not automatically resilience. Supporting many lightly used markets may fragment liquidity and spread governance resources thin.
Concentration brings its own tradeoffs. Larger markets become more important, and users on retiring networks lose a major lending venue. Aave governance must balance those costs against the benefits of deeper liquidity, clearer oversight and faster risk response.
The proposal’s transparent, rule-based approach can make that tradeoff more legible. Networks and asset issuers can see that continued support depends on economic activity, liquidity quality and manageable operational risk.
What Comes Next for Aave Users and Governance
The immediate next step is community review. Participants can challenge the selected reserves, proposed parameter sequence and assumptions about support costs. If the measure advances, formal governance actions will translate the plan into executable changes.
Implementation will likely occur in stages because each market has different debt, collateral and liquidity conditions. Risk providers will need to watch whether rate increases produce orderly repayment or create stress. Bridges and front ends may require coordination as deployments empty.
The broader signal extends beyond Aave. Mature DeFi protocols are moving from an expansion-first phase toward portfolio management, where removing products can be as important as launching them. Success depends on showing that exits are predictable, technically safe and fair to existing users.
The proposed Aave chain exits are not a rejection of multichain lending. They are an attempt to define the conditions under which a deployment remains worth supporting. If the wind-down proceeds smoothly, Aave could emerge with fewer markets, more concentrated liquidity and a clearer framework for deciding what belongs in its next stage.
