109-whitelist-balancer-claimer.md

Proposal 109. Whitelist Balancer's liquidity mining claimer

Voting link

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

Governance forum discussion

https://governance.aave.com/t/arc-whitelist-balancer-s-liquidity-mining-claim/9724

BGD analysis

Proposal types

🤝 partners

Context

This proposal enables an smart contract to claim on behalf of the Balancer Linear Pool the stkAAVE accrued on the rewards program, previously active on Aave v2 Ethereum.

Proposal creation

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

- id: 109
- creator: 0x55b16934c3661e1990939bc57322554d9b09f262
- executor: 0xee56e2b3d491590b5b31738cc34d5232f378a8d5
- targets: [0x9e0f13a2298a879c7834d84c2967fccc7fa42df8]
- values: [0]
- signatures: [execute()]
- calldatas: [0x]
- withDelegatecalls: [true]
- startBlock: 15768988
- endBlock: 15788188
- strategy: 0xb7e383ef9b1e9189fc0f71fb30af8aa14377429e
- ipfsHash: 0x8e3b44d853e826373be20553b8ab937043dec6952f5014e12bdb2d37f483f7c4

Technical analysis

We have verifier the proposal payload does the following:

1. Calls setClaimer() on the Aave IncentivesController, setting as claimer for the Balancer Vault the previously deployed claimer contract.

The claimer contract (StkAaveRetrieval) allows only the Balancer Multisig to claim for itself the rewards accrued on the Aave IncentivesController, by interacting with static aDAI, static aUSDC and static aUSDT.

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.

✅ BGD reviewed the procedure followed to submit the proposal.

✅ Only one payload used via delegatecall