[ARFC] Deprecation of Low Demand Volatile Assets on Aave V3 Instances

Overview

Following President Trump’s announcement of new tariffs on Chinese imports, financial markets experienced one of the sharpest declines in recent history. Within just 30 minutes, Bitcoin’s price plunged more than 12%, dropping from $116,500 to $102,700. Ether saw an even steeper decline of around 20%, and many other assets lost over 50–60% of their value within 10-minute intervals. This sudden market disruption sparked a wave of liquidation cascades across both DeFi and CeFi platforms.

During this period, we observed significant irregularities in oracle price feed behavior. Several assets exhibited extreme levels of volatility, introducing heightened risk to the protocol. Despite these unfavorable conditions, Aave remained resilient and maintained operational integrity throughout the market turbulence, avoiding critical failures or substantial bad debt.

In this analysis, we aim to evaluate the risks associated with these abnormal oracle behaviors and propose mitigation measures. Specifically, we recommend disabling the borrowability of a set of assets in order to reduce the protocol’s risk profile during periods of extreme volatility and stressed market conditions. Additionally, given the extreme levels of volatility for the covered assets, combined with the significant lack of revenue generated by their usage as collateral assets, we recommend setting their LTV to 0 and progressively deprecating their collateral status.

While Aave has been only minimally affected by these events, implementing these controls is essential to preserve the protocol’s stability and safeguard against future periods of elevated volatility risk.

Oracle Updates

The number of unique assets that registered a price update exceeding ±15% amounted to 16 across 7 distinct instances. This distribution of updates signals that the anomalies were not isolated events, but rather systemic. Some examples are:

Instance Asset Single Round_id Price Deviation
Optimism AAVE 62%
Ethereum AAVE 41%
Sonic wS -40%
Arbitrum ARB -36%
Ethereum CRV -33%

Such widespread oracle volatility presents protocol and systemic risks, as even short-lived pricing discrepancies can open arbitrage windows capable of draining liquidity or creating bad debt within lending markets.

Theoretical Framework

Periods of extreme volatility, particularly during sharp market downturns, can result in substantial dislocations between centralized exchange and on-chain prices. Such divergences often emerge when market liquidity becomes fragmented and price discovery across venues fails to synchronize. Under these conditions, protocols relying on siloed oracle price feeds are exposed to heightened systemic risk, as the reported prices may temporarily deviate from market prices on other venues, causing the protocols to accrue deficits.

When the oracle primarily references CEX prices while on-chain prices have not yet stabilized, substantial mispricing may arise. Suppose the protocol prices an asset X at PoX (the oracle price), while a DEX venue reflects a higher price ( PdX ) such that PdX > PoX . A market participant could exploit this price differential if another asset, Y, can be used as collateral, and its (1-liquidation threshold (LT)) is smaller than the price discrepancy.

In practice, the participant could supply $1M worth of asset Y, borrow ( LT * $1M ) of asset X, and sell X on DEX venues at the higher market price. This arbitrage can be repeated multiple times until either oracle and market prices converge or the protocol’s liquidity becomes constrained, thereby extracting value from the system and effectively transferring losses to the protocol.

To eliminate this class of risk, it is essential to restrict borrowing for selected assets that exhibit high volatility or are prone to severe price dislocations under stressed conditions. Marking these assets unborrowable is a targeted risk control measure that protects the protocol from exploits.

Case Studies

CRV/USDT

During the market crash, one notable instance of severe price dislocation occurred between the CRV/USD Chainlink oracle and the corresponding CRV/USDT Uniswap V3 pool, exposing Aave to a significant deficit. Specifically, the following contracts were involved:

  • CRV/USD Chainlink Oracle: 0xdA0DA298550E8E449b935CEA865c8100F3cA1b73
  • CRV/crvUSD/ETH Curve V2: 0x4eBdF703948ddCEA3B11f675B4D1Fba9d2414A14

Between blocks 23549969 and 23549976, the dislocation between the oracle-reported and DEX prices reached approximately 58%, persisting for several minutes. As illustrated in the chart below, Curve’s pool price lagged behind the oracle updates, only reaching $0.36, while the price feeds continued to reflect a severe drawdown, reaching $0.21.

This divergence effectively overvalued CRV on the protocol relative to on-chain market prices, which allowed an attacker to supply collateral to borrow underpriced CRV and sell it on-chain for an immediate profit, extracting value directly from the lending pool. While this specific exploit resulted in less than $200K of deficit, likely due to the relatively small pool size (~$2 TVL) and high price impact, the conditions highlighted a critical risk associated with asynchronous price updates and low-efficiency DEX markets.

ENS/WETH

Additionally, we have observed a similar exploit which has resulted in the user making over 17.5 WETH, as a result of oracle mispricing and low market efficiency of the Uniswap V3 pool, the contract addresses that enabled the transactions are:

  • ENS/USD Chainlink Oracle: 0x6Cc5173Ffd8d674C64f2DC7237730Ff021829865
  • ENS/WETH Uniswap V3: 0x92560c178ce069cc014138ed3c2f5221ba71f58a

During the period of mispricing, the user was able to collateralize a substantial amount of ENS debt, with 38.74 WETH and instantly sell the borrowed assets at a substantial profit of 17.58 WETH, leading to $95k of bad debt accrual.

Deficit Assets

The analysis above outlines both the theoretical and observed dynamics through which oracle mispricing can expose a lending protocol to systemic risk. To assess which assets present such risks, we examined price feed update patterns across multiple instances of Aave. Our reference threshold for assessing exploit potential is derived from the highest liquidation threshold (LT) on Aave’s Ethereum Core instance, WETH, with an LT of 83%. For an exploit to be economically viable, the oracle must underprice an asset by more than (1 – LT), or approximately 17%. Therefore, our screening focused on assets that exhibited price updates exceeding ±15%, as these represent of potential vulnerabilities.

As visualized in the chart above, 12 borrowable assets across various instances demonstrated abnormal oracle update behavior, characterized by large single-block percentage changes and delayed update times. Notably, ENS, CRV, and ARB, which each saw drawdowns ranging from 28% to 36% across Arbitrum and Ethereum instances, combined with the DEX venues’ low market efficiency, caused the protocol to accrue a deficit.

SVR Performance

We observed that the SVR oracle lagged by a constant 5 blocks (~60 seconds) throughout the crash period. Such latency can arise when (i) liquidations are economically unattractive due to oracle–DEX price divergences and high price impact, or (ii) liquidators are unable to participate due to technical constraints or infrastructure unavailability. In this event, SVR’s configuration could have been insufficient to support timely liquidations, thereby publishing the price updates with a consistent maximum allowed lag.

We have additionally observed that price feeds on Optimism have exhibited a substantial number of delays as compared to Ethereum and Arbitrum. The price feeds were likely stale on Optimism as a number of other assets have exhibited similar behavior, namely AAVE and LINK have registered their lowest prices approximately 6 - 8 minutes after the corresponding update on Ethereum, where the price had already recovered substantially.

As previously mentioned, the observed oracle desynchronization presents substantial risks for the protocol through discrepancy-driven arbitrage.

Borrow Revenue

While delisting volatile assets primarily aims to strengthen the protocol’s risk posture, we acknowledge the minor reduction in revenue this entails. Among the assets identified for delisting as borrowable, the largest YTD revenue contributor is CRV on Ethereum, at roughly $80K, with the remaining assets collectively adding just $37K. These figures are marginal in the context of overall protocol revenue and are far outweighed by the potential deficit and exploit risks highlighted by recent events. As such, disabling borrowing for these assets meaningfully enhances the protocol’s risk profile while only trimming a negligible portion of its income.

Collateral Revenue

As observed in the plots below, the outstanding long-tailed collateral assets, which currently reside in isolation mode, generate minimal revenue and utilization within the protocol, seeing just $6M in instantaneous aggregated collateralized debt and just $14K in revenue over the last three months, across CRV, UNI, LDO, CAKE, BAL, 1INCH and ENS. These modest revenue levels support the case for minimizing collateralization power, as the protocol faces an unfavorable risk–reward trade-off. Due to the high exploitability of the assets, which implies their elevated price volatility, substantial number of oracle deviations, and low market efficiency, we recommend setting the loan-to-value of the assets to zero, to limit the susceptibility of the protocol exploits on the collateral side.

Recommendation

With observed oracle dislocations across multiple markets, often reaching 15–50%, driven by market stress and asynchronous pricing between siloed oracles and on-chain venues, we recommend marking a set of assets as non-borrowable along with decreasing the LTVs to 0. Given the underlying volatility, documented oracle pricing delays, and low revenue contribution from these assets, this measure should have minimal impact on protocol income while significantly reducing exposure to volatility spikes and oracle desynchronization.

Looking ahead to Aave v3.6, where assets can be configured as borrowable within E-Modes only, we also recommend migrating a subset of these assets to E-Mode-restricted borrowing once available. This will limit risk to well-defined collateral sets, preserve market functionality, and maintain tighter risk constraints.

Specification

Instance Asset Current Borrow Cap Recommended Borrow Cap Current LTV Recommended LTV
ZkSync ZK 10,000,000 1 40% 0
Ethereum Core UNI 330,000 1 65% 0
Ethereum Core CRV 7,000,000 1 35% 0
Scroll SCR 28,000 1 - -
Ethereum Core BAL 1,000,000 1 57% 0
Celo CELO 400,000 1 55% -
Ethereum Core ENS 20,000 1 39% 0
Ethereum Core LDO 500,000 1 40% 0
Optimism LINK 84,000 1 66% -
Ethereum Core RPL 500,000 1 0% -
Optimism OP 1,300,000 1 58% -
BNB Cake 600,000 1 55% 0
Arbitrum ARB 14,510,000 1 58% -
Ethereum Core 1INCH 475,200 1 57% 0
Arbitrum LINK 183,000 1 66% -
Polygon LINK 58,000 1 66% -
Metis METIS 32,000 1 30% 0

Next Steps

We will move forward and implement the borrow cap updates via the Risk Steward process.

Disclosure

Chaos Labs has not been compensated by any third party for publishing this recommendation.

Copyright

Copyright and related rights waived via CC0.

6 Likes

Are you sure cake’s Borrow Cap should be set to 1?

The cakepad IDO is on fire, will be high demand for cake borrowing in the next few years, and last day’s CAKE borrowing apr is more than 100%.

Supportive, long-tail assets can be separately handled on specific hub on Aave V4.

3 Likes

Great work. I like this proposal. I also like the idea that Stani mention of revisiting these long-tail assets in Aave v4, where a dedicated spoke could manage them under tighter controls.

Crazy thinking, but this approach aligns naturally with Aave’s 2030 vision: first pruning low-demand assets in v3 so only stable “blue-chip” assets remain, then gradually deprecating less-used chains and focusing on high-liquidity markets, streamlining the protocol across fewer, more resilient markets for Aave v3. This also makes maintaining Aave v3 easier. If you think about it, it’s all coming together.

This proposal has full support from ACI, the risk/reward from long tail asset is simply not suited to justify maintenance of these assets inside the Aave ecosystem.

3 Likes

Summary

We support @ChaosLabs proposed deprecation of low-demand volatile assets on Aave V3 instances. The rationale is compelling: in times of market stress, these assets exhibit large price swings, oracle desynchronization, and arbitrage opportunities, all of which pose outsized risks to the protocol’s solvency.

By marking these assets non-borrowable and reducing their LTV to zero, the protocol renounces modest revenue streams while significantly bolstering its resilience against exploit vectors and bad debt accumulation. In our view, this is a prudent trade-off: reducing tail risk should take precedence over marginal protocol revenue.

Long-tail assets volatility

During the recent tariff-headline shock, Aave V3 Ethereum Core market experienced pronounced volatility and price dislocation across long-tail assets. Our analysis, conducted using Chainlink price feeds, shows that RPL suffered the largest drawdown, exceeding 70%, while CRV was the least affected at roughly 45%.


Source: LlamaRisk, October 20, 2025

Collateral asset demand

As of October 20, most of these asset reserves operate at very low utilization levels, typically below 30%, which means they generate minimal revenue for the protocol. Maintaining these assets as non-borrowable with an LTV of zero helps minimize the protocol’s insolvency risk and limits exposure to volatile, low-performing assets.

Instance Asset Borrow Cap Current Utilization Uopt
Ethereum RPL 500,000 64.37% 80%
Ethereum CRV 7,000,000 15.02% 45%
Ethereum BAL 1,000,000 4.02% 45%
Ethereum UNI 330,000 24% 45%
Ethereum LDO 500,000 13.45% 45%
Ethereum ENS 20,000 32.98% 45%
Ethereum 1INCH 475,200 7.37% 45%

We agree with @ChaosLabs initial asset list proposed for deprecation and are ready to coordinate for a smooth and timely deprecation process across all affected markets.

Disclaimer

This review was independently prepared by LlamaRisk, a DeFi risk service provider funded in part by the Aave DAO. LlamaRisk is not directly affiliated with the protocol(s) reviewed in this assessment and did not receive any compensation from the protocol(s) or their affiliated entities for this work.

The information provided should not be construed as legal, financial, tax, or professional advice.

To me, some of these assets can make sense to stay as collateral but only if there is a big actor like a chain DAO that decided to deposit them and borrow against them. It can be an alignment, yet it will also require having enough liquidity and low slippage on the chain for this asset.

Sorry if this is a dumb question, but what is the difference in the last table between “LTV 0” and “LTV -”

I’m assuming “LTV 0” is to make assets non-borrowable, and “LTV -” keeps the borrowable rate as it is.

1 Like

Dear Aave Community,

I strongly oppose the proposed deprecation of ARB on Aave V3’s Arbitrum instance. While I understand the intent to streamline operations and reduce risk, delisting ARB from its native chain would significantly harm its utility and the broader Arbitrum ecosystem.

ARB, as the governance token of Arbitrum, plays a critical role in the chain’s ecosystem. Allowing users to supply and borrow ARB on Aave V3 Arbitrum provides essential financial utility, enabling holders to leverage their assets for liquidity or yield opportunities without selling. Deprecating ARB would reduce its use cases, potentially impacting its value and adoption, which could indirectly affect the Arbitrum chain’s growth—where Aave V3 operates.

Even if utilization rates are currently low, ARB’s presence on Aave incentivizes user engagement and supports Arbitrum’s DeFi ecosystem. Instead of delisting, I propose exploring ways to boost ARB’s utilization, such as adjusting LTV ratios or incentivizing liquidity provision.

I urge the community to reconsider this deprecation and maintain ARB’s listing to preserve its utility and support the Arbitrum ecosystem. Let’s discuss alternatives to keep ARB active on Aave V3!

ARB is not proposed to be delisted, the current plan is not allowing people to borrow it as no one uses Aave to short it.

1 Like

people are also borrowing it

Hi AAVE Community,
I have a quick question regarding this proposal: will the collateral-to-borrow ratios (LTV) for assets like ARB, ETH, and AAVE remain the same after these changes?
For example, if it’s currently possible to borrow up to 58% of the value of ARB as collateral, will that ratio stay the same, or are any adjustments planned?

When there is a “-” on the case it means that value stay the same

Wait. What happen to current existing users? I borrow usdc using ENS, are we going to be liquidated when this’s deployed?

The mojority of the assets above would change the ratio. You can see the adjustment in the table. I’m not sure I understand it correctly: aave seems to plan to freeze current users (who use the assets above as collateral) ‘s borrow ability. They can’t borrow anymore. They need to exit or just freeze there. Correct me if I’m wrong here, please.

More importantly, I’m concerned that in some way somehow setting LTV to 0 indirectly trigger the liquidation. That would be scary. Moreover, is there any subsequent action to lower the liquidation threshold?

Hey @wartstone, altering the LTV to 0 does not affect the health of outstanding debt positions, rather deters the creation of existing debt positions with the specified collateral asset.

@ChaosLabs

“aave seems to plan to freeze current users (who use the assets above as collateral) ‘s borrow ability. They can’t borrow anymore. They need to exit or just freeze there. Correct me if I’m wrong here, please.”

So this statement is correct, right? Please help confirm on this cause if it’s not true, we need to worry about current position, which I believe there’re quite lots of people involved. (ENS total supplied $583.73K, CRV total supplied $5.07m, UNI even total supplied $6.98m.)

If it’s true, we may just need to focus whether aave would lower liquidation threshold later later.

Please help clarify this. I believe this matters to many people. Thanks

@wartstone, users that get these assets as collateral are not able to contract new debt (for example calling borrow function) before they exit the freezed asset from collateral. The freezing to not provoc direct liquidation

@Nandy.eth Assets above are already isolated mode. So it should not be the problem

@ChaosLabs Though I understand the point you made, I’m still not sure is there anything I didn’t know now which would indirectly trigger liquidation. Could u confirm that current users with these asset collateral would not be affected by this thing? All we need to focus is any subsequent liquidation threshold adjustment later. Thanks

It feels like this proposal is basically saying, “Look, these volatile assets keep putting the protocol at risk, and the revenue they bring in is tiny, so it is time to scale them back.” The data makes it clear that the recent price swings and slow oracle updates opened the door for bad trades that hurt the system. Turning off borrowing and dropping their LTV to zero sounds like a practical move that keeps Aave steady instead of letting a few unstable assets shake things up again. It is a small tradeoff for a much safer market