[ARC] Gauntlet Risk Parameter Recommendations (2023-03-20)

[ARC] Gauntlet Risk Parameter Recommendations (2023-03-20)

Simple Summary

After closely monitoring liquidity conditions across the markets following the USDC nonparity event, Gauntlet recommends the following parameter changes to mitigate risk to the protocol. These parameter changes aim to proactively manage risk following changes in liqudity.


Gauntlet Recommends decreasing the following caps AVAX v3:

  • FRAX supply cap from 50M to 1.5M.
  • FRAX borrow cap from 2M to 400k.
  • MAI supply cap from 50M to 1.5M.
  • MAI borrow cap from 2M to 500k.
  • BTC.b supply cap from 4.62k to 3k.
  • BTC.b borrow cap from 3.19k to 900.
  • USDC supply cap from 4B to 170M.
  • USDT supply cap from 2B to 260M.
  • WAVAX supply cap from 13.1M to 3.8M.
  • WETH supply cap from 113k to 40k.
  • WETH borrow cap from 62.1k to 11k.
  • DAI.e supply cap from 2B to 17M.

Gauntlet recommends adding the following caps AVAX v3:

  • Add 90M borrow cap to USDC.
  • Add 120M borrow cap to USDT.
  • Add 17M borrow cap to DAI.e.
  • Add 3M borrow cap to WAVAX.

ETH v3

  • Decrease CRV supply cap from 62.5M to 51M.

Our borrow and supply cap recommendations utilizes the methodology outlined in our borrow and supply cap methodology.


ETH v3

Asset Current Supply Cap Recommend Supply Cap Current Supply
CRV 62,500,000 51,000,000 108,000


Assets Current Supply Cap Recommend Supply Cap Current Supply Current Borrow Cap Recommend Borrow Cap Current Borrow
FRAX 50,000,000 1,500,000 15,340 2,000,000 400,000 10,230
MAI 50,000,000 1,500,000 7,870 2,000,000 500,000 5,717
BTC.B 4,620 3,000 4,620 3,190 900 373
USDC 4,000,000,000 170,000,000 51,670,000 - 90,000,000 33,030,000
USDT 2,000,000,000 260,000,000 28,090,000 - 120,000,000 21,310,000
WAVAX 13,100,000 3,800,000 2,970,000 - 3,000,000 1,230,000
WETH 113,000 40,000 18,290 62,150 11,000 3,368
DAI.e 2,000,000,000 17,000,000 7,010,000 - 17,000,000 4,350,000

Gauntlet’s Supply Cap recommendations would result in the effective freezing of supply on BTC.b market.

Next Steps

  • Welcome community feedback
  • Targeting AIP vote on 3/27/2023

Thanks for putting forward this proposal @seawolf.

We would like to flag that there is a proposal to update supply and borrow caps on V3 Avalanche, which was already approved by the community and will be executed by the Guardians shortly.

A table with the approved caps highlighted is shared below for visibility

Given the changes in on-chain liquidity on Avalanche, we support the update for USDC and DAI.e. In addition, with the current borrow of WAVAX exceeding the approved borrow cap, we support the recommendation for a 3M borrow cap.

For all other Avalanche recommendations, we do not believe there is a need for an additional update at this time.


Thanks, we have revised the proposal in the below table in order to avoid overlapping changes for AVAX v3 market. The existing approved recommendations on BTC.B would essentially freeze the supply on the market, and our recommendations on BTC.B further protects the market in case liquidity drops below the cap.


ETH v3

Asset Current Supply Cap Recommend Supply Cap Current Supply
CRV 62,500,000 51,000,000 108,000


Assets Current Supply Cap Recommend Supply Cap Current Borrow Cap Recommend Borrow Cap
BTC.B 4,620 3,000 3,190 900
USDC 4,000,000,000 170,000,000 - 90,000,000
WAVAX - 3,000,000
DAI.e 2,000,000,000 17,000,000 - 17,000,000

Gauntlet Update

Next steps for the ETH V3 changes (for CRV) have been posted here.

We will initiate a separate Snapshot vote for the AVAX V3 changes shortly, given that AVAX changes cannot be made via AIP.

1 Like

Snapshot vote has been published below. As a reminder, AVAX changes cannot be implemented via AIP, so this Snapshot vote serves as the community’s preference.


1 Like

The Snapshot vote for the AVAX changes has passed.

As an update, for AVAX V3, we will not move forward with the WAVAX change given market changes since the Snapshot but will move forward with the other cap changes for AVAX V3.

Thank you for this update. I do not understand the reasoning behind this recommendation for certain assets. LSDs and redeemable assets such as BTC.b cannot be viewed in the same lens as native assets.

Particularly for BTC.b and WETH.e it makes little sense for assets that can be bridged and arbitraged on demand to have such aggressive supply caps. Particularly, these assets do not require merchants or special fees to redeem and withdraw, they can be easily bridged.

Creating these arbitrary caps only forces liquidity to other venues who do not place arbitrary caps that need to consistently be raised on a manual basis (creating friction and inefficiencies). In my opinion and specifically in reference to the proposed changes to BTC.b, WETH.e, DAI.e, this is a pretty draconian measure for assets that have very little to do with the USDC depegging event.

Thanks for the question, @luigidemeo88.

This decision was made after Gauntlet’s analysis of the situation and considering various factors, which are detailed below. Extreme price movements can cause insolvencies in the protocol.
Approximately ~70% of all liquidations on Avalanche immediately trade out of their position. All of the BTC.b liquidations (13 total greater than 1,000 USD) in the last month immediately trade out of their positions. See these examples 1, 2, 3. That is the basis of considering on-chain liquidity for setting borrow and supply caps at this moment. The learning from the USDC price deviation was that DEX liquidity is a NECESSARY condition for liquidations on Aave V3 Avalanche. This condition seems to hold for BTC.b as well.
By lowering the caps, we aim to mitigate the risk of price manipulation attacks and protect the protocol’s growth. The cap we set relative to market caps is balanced to defend against attacks while still allowing for revenue generation.

  • Volume of bridged assets vs non-bridged assets: A significant amount of bridged assets like DAI.e left the ecosystem in comparison to non-bridged assets like USDT and USDC. This indicated a heightened level of risk and warranted a more conservative approach to managing the lending protocol.
    Recall that our borrow and supply caps serve to protect the protocol from price manipulation attacks, with liquidity being a key factor in the calculations. Please note the net outflows in BTC.b below.
  • Average time to bridge: The time taken to bridge assets is crucial in times of duress. Per the Avalanche docs, on average, it takes 1 hour to bridge to Avalanche from the Bitcoin network, and 20 minutes from Ethereum. Our aggressive recommendations take into account global liquidity, including liquidity in centralized exchanges. However, for bridged assets, this may hinder healthy liquidations from occuring during black swan events. By lowering the caps, we aim to encourage instantaneous liquidations and improve the stability of the protocol.

Lowering DAI.e caps was a pertinent response to the depeg, as during the event, the asset dropped 8% in price and resulted in $324K liquidated on the protocol (and a relatively small amount of insolvencies). As mentioned, in the process, a majority of the DAI.e liquidations instantaneously traded out of their positions. By reducing the caps, we aim to provide a more stable and secure lending environment, ensuring the long-term success and growth of the Avalanche Aave v3 lending protocol.

Please refer to our Supply and Borrow Cap Methodology for a detailed explanation of the factors considered in setting these caps. As this is a response to a crisis, we had opted to use conservative caps that reference only on-chain liquidity. Moreover, as outlined in this methodology, we propose slightly higher aggressive caps for some bridged assets in order to promote protocol usage and asset growth; however, this is secondary to protecting the protocol in times of volatility. We will continue to monitor liquidity conditions and make recommendations as they evolve.

A Note on LSTs

With respect to LSTs such as sAVAX, we had not recommended changes to sAVAX post-depeg, as the liquidity had widely recovered. We detail our methodology for setting borrow and supply caps for liquid staking tokens here, and welcome further discussion in that ARFC.

The above has been implemented. We thank the community for their participation.