As an update of the project, we have progressed the implementation and, after the feedback from the community and risk providers, the next steps are the following.
-
There is clear consensus that upper price protections for LSTs and stable-coins are a net improvement, and the initially proposed design, sound. Therefore, in order to prioritise delivery speed, we will proceed with an initial release applying those upper protections, leaving lower bounds for the following iteration (scheduled just after the first, as the security procedures will be simpler).
-
In order to reduce complexity, the correlated-asset price oracle will be applied initially on all the Aave v3 instances, with v2 left for the following iteration.
-
The assets to apply the solution on are the following:
Aave v3 Ethereum
USDT, USDC, rETH, DAI, cbETH, sDAI, LUSD, FRAX, crvUSD, wstETH
Aave v3 Polygon
MATICx, USDC.e, USDC, stMATIC, USDT, DAI, wstETH, agEUR
Aave v3 Avalanche
sAVAX, USDC, USDt, DAI.e, FRAX
Aave v3 Optimism
wstETH, USDC.e, USDT, sUSD, USDC, DAI, rETH, LUSD
Aave v3 Arbitrum
wstETH, USDC, USDT, USDC.e, DAI, rETH, LUSD, FRAX, EURS
Aave v3 Metis
m.USDC, m.USDT, m.DAI
Aave v3 Base
cbETH, USDbC, USDC, wstETH
Aave v3 Gnosis
wstETH, sDAI, xDAI, USDC, EURe
Aave v3 BNB Chain
USDC, USDT
-
Given their purely technical/risk nature, the final initial configurations will be defined at AIP stage, as they will based mainly on historic data on each one of the assets. We will request the risk providers of the community to recommend the most appropriate ones.
-
We will proceed now with the creation of an ARFC Snapshot, while the security procedures on the solution are finished.
The codebase can be found on https://github.com/bgd-labs/aave-capo with only minor naming and audit-related changes expected.