https://app.aave.com/governance/proposal/?proposalId=372
https://governance.aave.com/t/arfc-add-fxs-to-ethereum-v3/15112
💎 🆕 asset-listing
🔮 oracle-addition
This proposal lists FXS (Frax Share) on the Aave v3 Ethereum pool.
Transaction: https://etherscan.io/tx/0x181af826496924baba20d0c7457033bf3e0f29b22c9873e42e727c6334ecfb6c
- id: 372
- creator: 0x329c54289ff5d6b7b7dae13592c6b1eda1543ed4
- executor: 0xee56e2b3d491590b5b31738cc34d5232f378a8d5
- targets: [0x9aee0b04504cef83a65ac3f0e838d0593bcb2bc7]
- values: [0]
- signatures: [forwardPayloadForExecution((uint256,uint8,address,uint40))]
- calldatas: [0x00000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000001000000000000000000000000dabad81af85554e9ae636395611c58f7ec1aaec50000000000000000000000000000000000000000000000000000000000000012]
- withDelegatecalls: [false]
- startBlock: 18592893
- endBlock: 18612093
- strategy: 0xb7e383ef9b1e9189fc0f71fb30af8aa14377429e
- ipfsHash: 0xaf9ee1c1965d3483c0570f4d8a3e70744d08bc452e135331118169101af298c0
Proposal report
Payload report
The proposal payload correctly uses the BGD's Aave Config Engine of Aave v3 Ethereum, in this case, its listing features.
We have verified this payload respects the interface required by the v3 config engine and effectively configures the FXS listing with the following initial parameters:
-
The asset is enabled for borrowing and the interest rate strategy is configured the following way:
- Base variable borrow: 0%
- Variable borrow slope 1: 9%
- Variable borrow slope 2: 300%
- Optimal point: 45%
-
The asset is enabled as collateral in isolation
-
LTV: 35%
-
Liquidation Threshold: 45%
-
Liquidation Bonus: 10%
-
Liquidation Protocol fee: 10%
-
Reserve Factor: 20%
-
Supply cap: 800'000 FXS
-
Borrow cap: 500'000 FXS
-
Debt ceiling: 4'000'000 USD
-
No eMode category
-
Flashlonable
-
Not enabled for borrowing on isolation
The oracle used is a Chainlink FXS/USD.
The initial configuration is completely aligned with the pre-approved by the community on Snapshot
✅ The code on the proposal payload corresponds to the proposal specification.
✅ The proposal includes a proper tests suite, checking all necessary post-conditions.
✅ BGD reviewed the payload before the proposal was submitted.
✅ Only one payload used via delegatecall
✅ BGD reviewed the procedure followed to submit the proposal.