• © Goverland Inc. 2026
  • v1.0.8
  • Privacy Policy
  • Terms of Use
Event HorizonEvent Horizonby0xFAD69Bd739c64cC8e3f1C3bb3B60fe4f160174Cchvax.eth

[AAVE] Risk Parameter Updates - sAVAX on Aave V3 Avalanche

Voting ended over 1 year agoSucceeded

Simple Summary

A proposal to adjust sAVAX’s LT and LTV on Aave V3 Avalanche.

Motivation

Increasing the liquidation threshold and LTV for assets allows Aave to enhance users’ capital efficiency. However, this must be balanced with proper risk management to ensure that there is a sufficient buffer in the event of large drawdowns and/or liquidations. The analysis below was conducted utilizing our LT simulations, which showed either minimal or no increases in VaR at the recommended LT levels while also considering user distribution and on-chain liquidity.

sAVAX

sAVAX’s LTV and LT are currently set to 30% and 40%, respectively (its E-Mode parameters are 92.5% and 95%). The top suppliers are primarily looping sAVAX and WAVAX, reducing the risk of large-scale liquidations in this market. However, there is a small amount of non-WAVAX borrows against sAVAX, primarily WETH.e and stablecoins. Moreover, sAVAX maintains strong liquidity against AVAX, meaning that potential liquidations of sAVAX collateralized debt are likely to be completed efficiently. Given user distribution and liquidity, we recommend increasing LTV to 40% and LT to 45%.

Specification

Given these observations, we recommend making the following changes:

| Chain | Asset | Parameter | Current | Recommended | | | -- | |

  • | -- | | Avalanche | sAVAX | LTV | 30% | 40% | | Avalanche | sAVAX | Liquidation Threshold | 40% | 45% |

References

  • Implementation: AaveV3Avalanche
  • Tests: AaveV3Avalanche
  • Snapshot
  • Discussion

Copyright

Copyright and related rights waived via CC0.

https://app.aave.com/governance/v3/proposal/?proposalId=138

Off-Chain Vote

YAE
10 HVAXVC100%
NAY
0 HVAXVC0%
Download mobile app to vote

Discussion

Event Horizon[AAVE] Risk Parameter Updates - sAVAX on Aave V3 Avalanche

Timeline

Jul 30, 2024Proposal created
Jul 31, 2024Proposal vote started
Aug 02, 2024Proposal vote ended
Mar 26, 2026Proposal updated