https://app.aave.com/governance/proposal/?proposalId=240
https://governance.aave.com/t/arfc-add-lusd-to-aave-v3-on-arbitrum/12858
💎 🆕 asset-listing
🔮 oracle-addition
This proposal lists LUSD (LUSD Stablecoin, Liquity) on the Aave v3 Arbitrum pool.
Transaction: https://etherscan.io/tx/0x86b99f2fe51636b81a8bee9ca5848d88fd096482221a059f5a4bf3d408c1fc3e
- id: 240
- creator: 0x55b16934c3661e1990939bc57322554d9b09f262
- executor: 0xee56e2b3d491590b5b31738cc34d5232f378a8d5
- targets: [0xd1b3e25fd7c8ae7caddc6f71b461b79cd4ddcfa3]
- values: [0]
- signatures: [execute(address)]
- calldatas: [0x00000000000000000000000098bc9dfa3cecb37f1bdeadc6e774d39082756b19]
- withDelegatecalls: [true]
- startBlock: 17445126
- endBlock: 17464326
- strategy: 0xb7e383ef9b1e9189fc0f71fb30af8aa14377429e
- ipfsHash: 0x5d3ef37d565163c470206fb12e7b47ccb2b12894938e6a6454863be49aad9cc6
Ethereum
Arbitrum
We have verified the proposal uses correctly the Aave cross-chain governance system to communicate with Arbitrum.
The proposal payload correctly uses the BGD's Aave Config Engine of Aave v3 Arbitrum, in this case, its listing features.
We have verified this payload respects the interface required by the v3 config engine and effectively configures the LUSD listing with the following initial parameters:
-
The asset is enabled for borrowing and the interest rate strategy follows the parameters on the forum:
- Base variable borrow: 0%
- Variable borrow slope 1: 4%
- Variable borrow slope 2: 87%
- Optimal point: 80%
-
The asset is not enabled as collateral
-
Reserve Factor: 10%
-
Supply cap: 900'000 LUSD
-
Borrow cap: 900'000 LUSD
-
No eMode category
-
No isolation mode
-
Flashlonable
-
Not enabled for borrowing on isolation
The oracle used is the Chainlink LUSD/USD feed.
The initial configuration is completely aligned with the description on the Aave governance forum.
✅ 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.