https://app.aave.com/governance/proposal/?proposalId=186
https://governance.aave.com/t/arfc-supply-and-borrow-caps-update-wsteth-v3-arbitrum/12309
🔧 📊 params-update
This proposal updates multiple supply and borrow caps on Aave v3 Polygon and Arbitrum.
Transaction: https://etherscan.io/tx/0x3b49bed5329cccb61331c553171b678d87f512265d59ae1307a0745a1798f257
- id: 186
- creator: 0xbc540e0729b732fb14afa240aa5a047ae9ba7df0
- executor: 0xee56e2b3d491590b5b31738cc34d5232f378a8d5
- targets: [0x2e2b1f112c4d79a9d22464f0d345de9b792705f1,0x158a6bc04f0828318821bae797f50b0a1299d45b]
- values: [0,0]
- signatures: [execute(address),execute(address)]
- calldatas: [0x000000000000000000000000656482165fdf78f3fdd31d4ad4b518350766f3d5,0x000000000000000000000000656482165fdf78f3fdd31d4ad4b518350766f3d5]
- withDelegatecalls: [true,true]
- startBlock: 16876996
- endBlock: 16896196
- strategy: 0xb7e383ef9b1e9189fc0f71fb30af8aa14377429e
- ipfsHash: 0xb2323bc2ec23771a8e717c51e02debd7b72ec25f97cbbc5f66a8dbc979acff3f
Ethereum
Polygon
Arbitrum
Aave Seatbelt doesn't support Arbitrum yet.
We have verified the proposal uses correctly the Aave cross-chain governance system to communicate with Polygon and Arbitrum. The proposals payloads do the following:
By calling the PoolConfigurator of Aave v3 Polygon it changes the following caps:
- MAI (miMATIC) supply cap: 1'100'000 MAI -> 2'200'000 MAI
- MAI (miMATIC) borrow cap: 600'000 MAI -> 1'200'000 MAI
- stMATIC supply cap: 15'000'000 stMATIC -> 21'000'000 stMATIC
By calling the PoolConfigurator of Aave v3 Arbitrum it changes the following caps:
- wstETH supply cap: 2'400 wstETH -> 4'650 wstETH
- wstETH borrow cap: 190 wstETH -> 400 wstETH
✅ 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.