https://app.aave.com/governance/proposal/?proposalId=209
https://governance.aave.com/t/arfc-stmatic-supply-cap-increase-polygon-v3/12606
🔧 📊 params-update
This proposal updates supply caps of stMATIC on Aave v3 Polygon and WETH on Aave v3 Arbitrum.
Transaction: https://etherscan.io/tx/0xe5148fb2449cea2acb17c186356439f52879452cb2fb9c687ce4ddcf932a4295
- id: 209
- creator: 0x55b16934c3661e1990939bc57322554d9b09f262
- executor: 0xee56e2b3d491590b5b31738cc34d5232f378a8d5
- targets: [0x158a6bc04f0828318821bae797f50b0a1299d45b,0xd1b3e25fd7c8ae7caddc6f71b461b79cd4ddcfa3]
- values: [0,0]
- signatures: [execute(address),execute(address)]
- calldatas: [0x00000000000000000000000026366920975b24a89cd991a495d0d70cb8e1ba1f,0x0000000000000000000000004c68fda91bfb4683eab90017d9b76a99f2d77eed]
- withDelegatecalls: [true,true]
- startBlock: 17133249
- endBlock: 17152449
- strategy: 0xb7e383ef9b1e9189fc0f71fb30af8aa14377429e
- ipfsHash: 0x6b17a57b2585c7716fb784ac9f5d4c6c493db227a643698c40666c2463ecbd5c
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:
This payload is correctly created with the new BGD's Aave Config Engine of Aave v3 Polygon as target, doing the following changes:
- stMATIC supply cap: 21'000'000 stMATIC -> 25'000'000 stMATIC
This payload is also correctly created with the new BGD's Aave Config Engine of Aave v3 Arbitrum as target, doing the following changes:
- WETH supply cap: 35'280 WETH -> 45'000 WETH
✅ 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.