[ARFC] Chaos Labs - Borrow Cap Reductions on Aave Ethereum - 03.11.24

Summary

Reduce Borrow Caps for long-tailed assets on Aave V3 Ethereum.

Motivation

As part of our ongoing strategy to minimize theoretical exposure to long-tailed debt on Aave, this proposal aims to mitigate the impact of volatility in debt assets further by implementing a substantial reduction in Borrow Cap values. Borrowing these assets typically yields minimal revenue but can pose significant risks, particularly in scenarios where liquidating these positions necessitates obtaining the underlying asset during a large pump. Given the recent upward volatility in asset prices, we propose a refined methodology for determining and implementing these Borrow Cap reductions. This approach aims to enhance the protocol’s resilience and stability amidst dynamic market conditions, safeguarding the interests of Aave users and stakeholders.

Screenshot 2024-03-01 at 16.35.20
Long-tail asset debt as % of the total debt on Aave V3 on Ethereum

Methodology

The recent 50% price surge in UNI within an hour-long timeframe on February 23rd, triggered by the activation of a fee distribution proposal for token holders, resulted in a significant shortfall on Compound. While this was attributed to inadequate dual-bounded fallback oracle logic on Compound, a feature not employed by Aave, the subsequent mispricing of UNI debt and upward debt asset volatility highlighted broader market sentiments favoring risk-taking. In the context of Aave, it becomes imperative to define parameters that account for debt dynamics concerning Chainlink oracle feed latency and update frequency, particularly during periods of rapid price pumps. Therefore, leveraging the UNI/USD Chainlink feed data during the UNI pump as a means to assess Chainlink latency practices can be used to mitigate similar risks in the future.

UNI/USD Chainlink Feed Update Frequency (Hour of UNI Pump)

Screen Shot 2024-03-11 at 22.39.01

UNI/USD Chainlink Feed Update Frequency (Day of UNI Pump)

Screen Shot 2024-03-11 at 22.39.08

During the recent 50% UNI price surge, the UNI/USD Chainlink feed displayed a total of 64 updates within the hour. Notably, the maximum price change between any two updates reached 4.6%, occurring within just two blocks, underscoring the significance of rapid fluctuations in asset prices.

Expanding upon this, the UNI’s positive price change of 4.6%, coupled with other significant deviations from the recent pump, represents the most substantial movement observed over the last 10,000 oracle updates.

Screenshot 2024-03-05 at 11.13.31

Upon excluding the data pertaining to the pump, the maximum positive price change diminishes to just 2.5%.

Screenshot 2024-03-05 at 11.27.24

Given that Borrow Caps are denominated in tokens, it’s crucial to recognize that a proportional increase in the underlying asset’s price will directly translate to a linear rise in dollar-denominated Borrow Caps. In light of these observations, it becomes imperative to establish stress-tested assumptions and parameters to reinforce this framework, ensuring its resilience and effectiveness amidst dynamic market conditions. These are all worst-case assumptions to derive a conservative parameter set that will protect from bad debt even in such cases:

Assumptions:

  1. We formally refer to the maximum UNI oracle price change from the last update as
    Screen Shot 2024-03-11 at 22.46.35, where time Screen Shot 2024-03-11 at 22.47.38 is the time at which this price jump in the debt asset occurs. We utilize this maximum price change value as an input within our formula below.
  2. The underlying debt asset has undergone a rapid 50% surge in value, reminiscent of the UNI token’s price movement while retaining linearity in the context of on-chain liquidity distribution.
  3. We assume that the Borrow Cap is at 100% utilization.
  4. At time Screen Shot 2024-03-11 at 22.48.50 all borrowers uniformly possess an LTV ratio equivalent to Screen Shot 2024-03-11 at 22.50.24. This ensures that the debt value upon liquidation eligibility at time Screen Shot 2024-03-11 at 22.47.38 is overvalued by approximately Screen Shot 2024-03-11 at 22.52.28, or 4.6%, given the assumption that the stable collateral asset i with the highest LT on Aave Ethereum serves as collateral.
  5. The Screen Shot 2024-03-11 at 22.52.28 update indicates the final update at which the 50% price surge has been reached, prior to liquidations occurring.
  6. Our Screen Shot 2024-03-11 at 22.55.43 assumption is based on our proposal to decrease LTs for stablecoins, returning a value of 78% on Ethereum.

Under these extreme assumptions, we define a final targeted price impact formula, denoted as Screen Shot 2024-03-11 at 22.56.33, to approximate a risk-averse Borrow Cap value.
Screen Shot 2024-03-11 at 22.57.41

In essence, this expression represents the critical threshold for price impact, beyond which the liquidation of all positions tied to the underlying debt asset can occur without risking bad debt accumulation on the platform, even under highly adverse conditions. We now introduce a new variable, denoted as Screen Shot 2024-03-11 at 23.02.35, which represents the token output or value as a function of the targeted price impact set at 12.3% for a specific debt asset i. This is the expected amount that can be safely liquidated under an extreme scenario. This variable serves as a safeguard against adverse scenarios, such as a significant surge in the underlying debt asset’s price, resulting in an entire Borrow Cap’s worth of debt nearing liquidation, compounded by an “overpriced” oracle.
For assets with ample liquidity where the current Borrow Cap exceeds the indicated price impact values, or the current borrow usage surpasses the
Screen Shot 2024-03-11 at 23.02.35, we simply employ a normalization approach by adjusting the current values in dollar terms to accommodate a 50% increase in the underlying assets. More formally, Screen Shot 2024-03-11 at 23.03.41, where Screen Shot 2024-03-11 at 23.08.42 refers to the current Borrow Cap denominated in tokens for all debt assets i.

Computing our Borrow Cap recommendations for each asset i:
Screen Shot 2024-03-11 at 23.04.38

Specification

Screen Shot 2024-03-11 at 23.04.59

Next Steps

  1. Following community feedback, submit the ARFC for a snapshot vote for final approval.
  2. If consensus is reached, submit an Aave Improvement Proposal (AIP) to implement the proposed updates.

Disclaimer

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

Copyright

Copyright and related rights waived via CC0

2 Likes

I do agree that we should mitigate risk as much as possible here and maybe should go one step further and create a framework for new assets. @eboado already proposed something like this, like have a threshold of fees an assets must generate within a time frame.

Also I want to highlight the MKR token here. I do remember there was a user that wanted to migrate from v2 to v3 but wasn’t able, has the wasn’t enough space for him. He said he was the largest maker supplier here. So maybe revisit this and check what’s the current status on this one.

2 Likes

@ChaosLabs Can you unpack the formula a bit more and explain how it achieves the desired goal? Also, in the 2nd term of the min term for the recommended borrow cap, why is there a division by 1.5 (or multiplication by 2/3s)?

So if I am understanding things correctly, this means that by default we are considering reducing the caps by 1/3 and then seeing if this computed price impact term gives a more conservative cap?

is this a one time application of this formula or is this the borrow cap methodology going forward? How are we to think about this formula long term?

We have published a Snapshot for the community to vote on, starting in 24h.

We thank you in advance for your participation in the vote.

@ChaosLabs thanks for this.

Is the formula based on the assumption of a 50% increase in price at the same pace as the UNI price increase? In that case, are we being too conservative with this assumption for the borrow cap, or is this fine given the long-tail nature of these assets?

2 Likes

Thank you for the feedback on this proposal:

@sid_areta - Yes. Given UNI’s relatively lower long-tail asset status, the minimal revenue accrual of the mentioned assets, and the current high volatility in the market, we believe it’s reasonable to apply a conservative approach when analyzing theoretical scenarios in this context. In addition, please note that these updates do not currently block additional borrows for the given assets.

@EzR3aL - Absolutely, developing a concrete and continuous borrow cap framework for long-tailed assets is a priority initiative in our pipeline. Regarding the MKR user, this proposal only updates the borrow caps and does not pose a constraint on migration of positions from V2

@midapple - By leveraging a recent extreme event, we aim to mitigate potential future shortfalls by minimizing cumulative borrowing power for long-tailed assets, particularly considering the highly volatile market conditions. Moving forward, we plan to implement a more structured framework based on this logic, enabling us to offer continuous borrow cap recommendations tailored to the variables mentioned.

3 Likes

AIP-65 has been published for this proposal, with voting starting in less than 24h.

Thank you in advance for your participation in the vote.

1 Like