Skip to content

Latest commit

 

History

History
93 lines (54 loc) · 3.47 KB

130-aave-v3-polygon-addition-emission-admins.md

File metadata and controls

93 lines (54 loc) · 3.47 KB

Proposal 130. (REPETITION OF 128) Aave v3 Polygon - addition of EMISSION_ADMINs for LDO, stMATIC, MaticX and SD


Voting link

https://app.aave.com/governance/proposal/?proposalId=130


Governance forum discussion

https://governance.aave.com/t/arc-stmatic-maticx-emission-admin-for-polygon-v3-liquidity-pool/10632

https://governance.aave.com/t/arc-ldo-emission-admin-for-polygon-v3-liquidity-pool/10575

https://governance.aave.com/t/arc-sd-emission-admin-for-polygon-v3-liquidity-pool/10658


BGD analysis


Proposal types

🔗 🌉 cross-chain execution

🎁 rewards


Context

This proposal sets EMISSION_ADMIN roles for different entities to configure rewards of LDO, stMATIC, MATICX and LDO, on Aave v3 Polygon. Important to highlight that this is an exact repetition of proposal 128.


Proposal creation

Transaction: https://etherscan.io/tx/0x6bea173aa8314737aff18b2c58b85a228eb81b34fd22c7e202748b9f07ec3507

- id: 130
- creator: 0x55b16934c3661e1990939bc57322554d9b09f262
- executor: 0xee56e2b3d491590b5b31738cc34d5232f378a8d5
- targets: [0x158a6bc04f0828318821bae797f50b0a1299d45b]
- values: [0]
- signatures: [execute(address)]
- calldatas: [0x0000000000000000000000007e8f833d23e19e88e3781ca913d674a2d5178fa1]
- withDelegatecalls: [true]
- startBlock: 16176459
- endBlock: 16195659
- strategy: 0xb7e383ef9b1e9189fc0f71fb30af8aa14377429e
- ipfsHash: 0x780a2b877ea3b13c924a30d2959ea0b8f0257799f1d4d743ed58f8783f529954

Aave Seatbelt report

Ethereum report:

https://github.com/bgd-labs/seatbelt-for-ghosts/blob/main/reports/Aave/0xEC568fffba86c094cf06b22134B23074DFE2252c/130.md

Polygon report:

https://github.com/bgd-labs/seatbelt-for-ghosts/blob/main/reports/Aave/0xEC568fffba86c094cf06b22134B23074DFE2252c/130_fx_8_0.md


Technical analysis

From a technical point of view, we have verified that:


BGD validations

✅ 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.