Avalanche
Aave's deployment on the Avalanche C-Chain
Following the Aave DAO snapshot approval, V3 of the Aave Protocol has been deployed on Avalanche. Avalanche is one of the fastest smart contracts platforms in the blockchain industry, as measured by time-to-finality, and has the most validators securing its activity out of any proof-of-stake protocol. Avalanche’s C-Chain is an instance of the EVM running with Avalanche’s consensus.
Asset | eMode Params | Borrow | Siloed | Collateral | Borrow Isolation | LTV | Liq. Thresh | Liq. Bonus | Debt Ceil | Supply Cap | Borrow Cap | Reserve Factor |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
DAI |
| Yes | No | Yes | Yes | 75% | 80% | 5% | - | 2B | 0 | 10% |
USDC |
| Yes | No | Yes | Yes | 82.5% | 85% | 4% | - | 2B | 0 | 10% |
USDT |
| Yes | No | Only Isolation Mode | Yes | 75% | 80% | 5% | 5M | 2B | 0 | 10% |
AAVE |
| No | No | Yes | No | 60% | 70% | 7.5% | - | 0 | 0 | 0% |
LINK |
| Yes | No | Yes | No | 50% | 65% | 7.5% | - | 0 | 0 | 20% |
WBTC |
| Yes | No | Yes | No | 70% | 75% | 6.5% | - | 0 | 0 | 20% |
WETH |
| Yes | No | Yes | No | 80% | 82.5% | 5% | - | 0 | 0 | 10% |
WAVAX |
| Yes | No | Yes | No | 65% | 70% | 10% | - | 0 | 0 | 20% |
The reserve factor aka treasury collector contract can be found at 0xaCbE7d574EF8dC39435577eb638167Aca74F79f0
The price update frequency results from the liquidation strategy. We follow a margin method, in which prices are refreshed every time the deviation crosses a certain threshold. We use Chainlink’s decentralised oracles for the price feeds.
Pair Data Feed | Deviation Threshold | Oracle Contract Address |
|---|---|---|
0.5% | ||
0.5% | ||
1% | ||
0.5% | ||
0.1% | ||
0.5% | ||
0.1% | ||
0.5% | ||
0.1% | ||
0.1% |
Token | AToken | Stable Debt Token | Variable Debt Token | Interest Rate Strategy |
|---|---|---|---|---|
Aave team do not hold any keys to the multisig controlling Aave V3 markets on Avalanche
During an initial bootstrapping phase, the Avalanche deployment is controlled by a multisig (keys held by Avalanche community) and follows the same security practices implemented during the governance transition period for Aave V1 and V2.
Last modified 5mo ago