Skip to content
RiverCore
Aave Cuts 75 Reserves and Six Chains in Risk Retrenchment
Aave reservesDeFi governanceblockchain deploymentAave cuts 75 reserves six chainsAave liquidity concentration strategy

Aave Cuts 75 Reserves and Six Chains in Risk Retrenchment

30 Jul 20267 min readSarah Chen

Aave is retiring 75 asset reserves and pulling out of six blockchain deployments in one governance sweep, touching roughly $98 million in supplied assets against $15.6 million in outstanding debt. That is a supply-to-debt ratio of about 6.3 to 1 on the affected positions, which tells you something before you read another line: these are markets where lenders showed up and borrowers largely did not. Founder Stani Kulechov announced the changes on X on July 29, with the mechanics documented in an accompanying governance proposal.

What Happened

The cleanup comes in three parts. First, 50 underused reserves are being removed across Aave's largest deployments: Ethereum, Arbitrum, Base, Polygon, Avalanche, Optimism, Gnosis and BSC. Second, as DailyCoin reported, Aave is exiting six smaller deployments entirely: Sonic, Scroll, zkSync, Metis, Soneium and Aptos, which removes another 25 reserves. Third, 21 matured Pendle Principal Tokens are being rotated into fresh maturities, a housekeeping step rather than a strategic retreat.

The dollar split is instructive. Reserve removals across the majors account for $85.3 million supplied and $11.5 million borrowed. The six full-market exits account for only $12.8 million supplied and $4.1 million borrowed. Put differently: the six chains Aave is leaving hold about 13 percent of the supply value being touched by this proposal, but 26 percent of the borrow value. Borrowers on Sonic, Scroll, zkSync, Metis, Soneium and Aptos were relatively more active than their supplier base, but the absolute numbers are small enough that Aave clearly does not consider these deployments load-bearing.

Nothing gets guillotined. Aave will freeze new activity in affected markets, reduce borrowing and supply caps, and raise reserve factors to nudge users toward closing positions. The source does not disclose the exact freeze schedule or a hard deadline for full deprecation, which matters because the wind-down duration determines how much liquidation risk suppliers absorb on the way out. Kulechov attributed the sweep to Aave's newly established Risk Framework and Technical Asset Listing Framework, and the proposal explicitly frames it as proactive maintenance rather than a reaction to any single incident.

Technical Anatomy

The mechanism Aave is using here is textbook DeFi wind-down, but the parameter choices are worth reading closely. Freezing a reserve on Aave means no new supply and no new borrow, while existing positions can still be repaid, withdrawn, or liquidated. Lowering supply and borrow caps prevents late arrivals from adding to the position stack. Raising the reserve factor, the share of interest that accrues to the protocol treasury rather than to suppliers, degrades the yield on holding the position, which is the incentive lever pushing users to exit voluntarily.

That last knob is the interesting one. Aave is effectively taxing patience. A supplier who ignores the deprecation notice earns less over time than one who withdraws and redeploys into an active reserve. The design avoids the two failure modes of a hard shutdown: forced liquidations that dump collateral into thin markets, and stranded debt where borrowers cannot exit because the corresponding supply side has already fled. In an EVM lending market, the utilization curve and interest rate model do most of the work if you set the parameters right, so Aave does not need to intervene beyond the config layer.

The six-chain exit is a different animal. Deprecating a full deployment means Aave stops maintaining oracle feeds, risk parameter updates, and governance attention for that network. Even if the smart contracts remain on-chain, an unmaintained lending market is a security liability. Stale oracle prices are the single most common vector for lending protocol exploits, and every additional chain multiplies the surface area for oracle drift, bridge risk, and validator-level assumptions. Concentrating on Ethereum plus the major L2s and sidechains reduces the number of independent trust assumptions Aave has to underwrite. We do not know from the source what the ongoing per-chain maintenance cost was in engineering hours or oracle fees, but the bound is clearly non-trivial or governance would not have voted to eat the reputational cost of pulling out.

If Aave's Risk Framework is enforced consistently, we should see further reserve deprecations announced within the next two governance cycles, and the total count of Aave-supported networks should either hold flat or decline through the rest of 2026.

Who Gets Burned

Start with the obvious losers: the six chains losing their Aave deployment. Sonic, Scroll, zkSync, Metis, Soneium and Aptos each lose their marquee lending venue, or at minimum the credibility signal of being an Aave-supported chain. For newer chains still competing for TVL narrative, losing Aave is not fatal, but it is the kind of quiet demotion that shows up in ecosystem reports six months later. Scroll and zkSync in particular were positioned as tier-one zkEVM destinations, and their exclusion from Aave's supported set is the more surprising line on the list.

Suppliers currently holding positions in the affected reserves are the second exposed group. As reserve factors rise and caps tighten, their yields compress. Anyone lazy about migrating will simply earn less. Borrowers face the mirror image: with borrow caps falling, refinancing on the same chain and same protocol may not be possible, so they either repay from external liquidity or move debt to a competitor.

Competing lending protocols are the ambiguous case. Morpho, Radiant, Compound v3, and chain-native lenders on Scroll, zkSync, and Aptos now have an opening to absorb the migrating users. Whether they take that opening depends on whether they can price risk on the same long-tail assets Aave just decided were not worth carrying. If those assets were unprofitable at Aave's scale, they are almost certainly unprofitable at a smaller competitor's scale, so I would expect the reserve removals to accelerate consolidation rather than redistribute activity.

The unanswered question, and the one I would flag hardest: how much of the $15.6 million in outstanding debt is held by a small number of large borrowers versus a long tail? The source does not disclose the distribution. If it is concentrated, the wind-down is easy. If it is fragmented across hundreds of small positions on chains where gas or bridge costs are non-trivial, some of that debt will simply sit until liquidation. Testable bound: if concentration is high, expect the debt figure to drop below $5 million within 60 days of the freezes taking effect.

Playbook for Crypto and DeFi

For teams building on the six exiting chains, this week's action item is a liquidity audit. Identify every protocol integration that depends on Aave as a money-market backstop, whether for flash loans, aToken collateral, or rate-benchmark oracles. Anything routing through Aave on Sonic, Scroll, zkSync, Metis, Soneium or Aptos needs a fallback path before caps tighten further.

For treasury and DeFi ops teams with positions on Aave, pull a per-reserve report and cross-check against the governance proposal's deprecation list. Suppliers should exit voluntarily before reserve factor hikes bite. Borrowers should refinance now rather than during the tail end of the wind-down, when available liquidity on the exit path will be thinner.

For protocol designers, the useful lesson is in the Risk Framework itself. Aave is signaling that continuous risk assessment applies across all deployments, meaning any reserve can be marked for deprecation as usage data evolves. Building integrations that assume permanent availability of a specific Aave market is now a documented mistake. Design for reserve-level substitutability, not chain-level permanence.

For anyone underwriting cross-chain lending exposure more broadly, the multi-chain expansion thesis that defined 2022 to 2024 is being unwound in public. Expect Morpho, Compound, and Spark to face similar governance debates within the next two quarters. Prediction: at least one more top-ten lending protocol announces a chain deprecation before the end of Q4 2026.

Key Takeaways

  • Aave is removing 75 reserves and six full deployments, affecting $98M supplied and $15.6M borrowed, a 6.3-to-1 supply-to-debt ratio that flags these as lender-heavy, borrower-light markets.
  • The wind-down uses frozen activity, lower caps, and higher reserve factors rather than hard shutdowns, taxing patience instead of forcing liquidations.
  • The six exiting chains (Sonic, Scroll, zkSync, Metis, Soneium, Aptos) lose a marquee lending venue; Scroll and zkSync are the most surprising cuts on the list.
  • Unknown: the concentration of the $15.6M outstanding debt. High concentration means a clean wind-down in under 60 days; a long tail means stranded positions.
  • Expect further Aave deprecations within two governance cycles and at least one peer protocol to announce similar cuts by end of Q4 2026.

Frequently Asked Questions

Q: Which blockchains is Aave exiting?

Aave is fully exiting six smaller deployments: Sonic, Scroll, zkSync, Metis, Soneium and Aptos. These six exits remove 25 asset reserves and account for $12.8 million in supplied assets and $4.1 million in outstanding debt.

Q: What happens to users with existing positions on the affected Aave markets?

Aave is not shutting the markets down abruptly. It will freeze new activity, lower borrowing and supply caps, and raise reserve factors to encourage users to close positions voluntarily. Existing suppliers and borrowers can still withdraw or repay, but yields on affected reserves will degrade over time.

Q: Why is Aave reversing its multi-chain expansion?

Founder Stani Kulechov tied the cleanup to Aave's newly established Risk Framework and Technical Asset Listing Framework, framing it as proactive risk management rather than a reaction to any single incident. The move concentrates liquidity on higher-usage markets and reduces the operational and security overhead of maintaining low-adoption deployments.

SC
Sarah Chen
RiverCore Analyst · Dublin, Ireland
SHARE
// RELATED ARTICLES
HomeSolutionsWorkAboutContact
News06
Dublin, Ireland · EUGMT+1
LinkedIn
🇬🇧EN▾