https://app.aave.com/governance/proposal/?proposalId=149
https://governance.aave.com/t/arc-add-support-for-cbeth/10425
💎 🆕 asset-listing
🔮 oracle-addition
This proposal lists cbETH (Coinbase Wrapped Staked ETH) on the Aave v3 Ethereum pool.
Transaction: https://etherscan.io/tx/0xb256802f9d5372ff726db0ae9dcfecc03258baef46fb290bf7f02951e1aafcc2
- id: 149
- creator: 0x62a43123fe71f9764f26554b3f5017627996816a
- executor: 0xee56e2b3d491590b5b31738cc34d5232f378a8d5
- targets: [0xd91d1331db4f436daf47ec9dd86decb8eef946b4]
- values: [0]
- signatures: [execute()]
- calldatas: [0x]
- withDelegatecalls: [true]
- startBlock: 16543915
- endBlock: 16563115
- strategy: 0xb7e383ef9b1e9189fc0f71fb30af8aa14377429e
- ipfsHash: 0x05097b8a0818a75c1db7d54dfd0299581cac0218a058017acb4726f7cc49657e
The proposal payload follows the new approach for listings, using the Aave V3 listing engine contract, containing logic to expose a simple interface for listings, and do proper validations.
We have verified this payload respects the interface required by the v3 listing engine and effectively configures the cbETH 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: 7%
- Variable borrow slope 2: 300%
- Optimal point: 45%
- LTV: 67%
- Liquidation Threshold: 74%
- Liquidation Bonus: 7.5%
- Reserve Factor: 15%
- Liquidation protocol fee: 10%
- Supply cap: 10'000 cbETH
- Borrow cap: 1'200 cbETH
- No eMode category
- No isolation mode
- Flashlonable
- Not enabled for borrowing on isolation
We have deployed the oracle adapter connected to the asset, and verified it works correctly, by using the underlying ETH/USD and cbETH/ETH Chainlink price feeds.
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.