Whitelist Balancer’s Liquidity Mining Claim
01Summary
This proposal enables Balancer DAO to retrieve approximately 1,500 stkAAVE liquidity mining rewards that have accumulated in three Linear Pools (aDAI, aUSDC, aUSDT) within the Balancer Boosted Aave Pool. The changes allow the Balancer Multisig to claim and transfer these rewards, which the Linear Pools cannot manage themselves.
- Type
- protocol addition
- Funding
- $1500 stkAAVE (amount in USD not specified)
Key changes
- Sets the Retrieval Contract as the claimer of Balancer DAO's stkAAVE rewards from Aave Linear Pools(high)
- Enables the Balancer Multisig to call the Retrieval Contract to claim stkAAVE on behalf of Balancer DAO from aDAI, aUSDC, and aUSDT Linear Pools(high)
- Transfers claimed stkAAVE rewards to the Balancer Multisig wallet(high)
Generated by Kvorum
02Description
Simple Summary
This proposal enables Balancer DAO to retrieve the stkAAVE Liquidity Mining incentives distributed to Linear Pools in the Balancer Boosted Aave Pool.
Abstract
Balancer DAO seeks to retrieve around 1,500 stkAAVE from several Linear Pools. Balancer DAO accrued this stkAAVE after it deposited liquidity into Aave while Liquidity Mining incentives were being distributed [1,2].
The proposal is to implement the changes required to enable Balancer DAO to retrieve the stkAAVE from the Linear Pools within the Balancer Boosted Aave Pool.
Motivation
Three Linear Pools within the Balancer Boosted Aave Pool have accrued around 1,500 stkAAVE from Liquidity Mining rewards, [3].
The Linear Pool holds the aTokens and receives the stkAAVE liquidity mining rewards but can not call the claimRewards function or manage any stkAAVE if it was received.
The Linear Pools unable to call getUnclaimedRewards() with 0xba12222222228d8ba445958a75a0704d566bf2c8 are detailed below:
- 0x02d60b84491589974263d922d9cc7a3152618ef6
- 0xd093fa4fb80d09bb30817fdcd442d4d02ed3e5de
- 0xf8fd466f12e236f4c96f7cce6c79eadb819abf58
Aave enables other addresses to claim on behalf of smart contracts using the claimOnBehalfOf() function.
Specification
A full specification of the payload contract and tests enabling this mandate can be found on the Llama Github here
The Proposal Payload does the following:
- Sets the claimer of the Balancer DAO contract's stkAAVE rewards to be the Retrieval Contract.
The retrieval contract does the following:
- It can only be called by the Balancer Multisig: 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f.
- It claims the stkAAVE rewards on behalf of the Balancer DAO: 0xba12222222228d8ba445958a75a0704d566bf2c8 from aDAI, aUSDC, and aUSDT Balancer Linear Pools.
- It transfers the stkAAVE rewards to the Balancer Multisig: 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f.
Snapshot and forum discussion can be found at reference [6] and [7].
Test Cases
This proposal has been tested and peer reviewed by Bored Ghost Developing [5], including simulations on mainnet of the whole proposal lifecycle.
Test cases can be found at reference [8].
Implementation
Payload Implementation and Retrieval Contract can be found at reference [9] & [10] respectively.
Deployed Contracts
- Proposal Payload = 0x9e0f13a2298a879c7834d84c2967fccc7fa42df8
- Retrieval Contract = 0x0e2d46fe246eb926d939a10efa96fb7d4eb14bb3
References
- https://docs.balancer.fi/products/balancer-pools/boosted-pools#linear-pools
- https://governance.aave.com/t/arc-continue-liquidity-mining-program-on-aave-v2-ethereum-market-and-introduce-liquidity-mining-on-aave-arc-market/7189
- https://app.balancer.fi/#/pool/0x7b50775383d3d6f0215a8f290f2c9e2eebbeceb20000000000000000000000fe
- https://etherscan.io/address/0x10a19e7ee7d7f8a52822f6817de8ea18204f2e4f
- https://twitter.com/bgdlabs
- https://snapshot.org/#/aave.eth/proposal/0xdaa660ea59f8678748d6f133d7d7ed70b941798aa9a0044a16a1285d09e26bf5
- https://governance.aave.com/t/arc-whitelist-balancer-s-liquidity-mining-claim/9724
- https://github.com/llama-community/aave-stkaave-retrieval/blob/main/src/test/StkAaveRetrievalE2E.t.sol
- https://github.com/llama-community/aave-stkaave-retrieval/blob/main/src/ProposalPayload.sol
- https://github.com/llama-community/aave-stkaave-retrieval/blob/main/src/StkAaveRetrieval.sol
Copyright
Copyright and related rights waived via CC0.
03Mismatch analysis
The proposal's calldata contains a single action: a call to execute() on the address explicitly identified in the description as the 'Proposal Payload' contract (0x9e0f13a2298a879c7834d84c2967fccc7fa42df8). This matches the address given in the Deployed Contracts section exactly. Aave-style governance proposals commonly encode their entire logic as a single execute() call that delegatecalls into a payload contract, which then performs the substantive state change (here, setting the claimer of Balancer DAO's stkAAVE rewards to the Retrieval Contract) as described in the Specification section. Because the decoded action only shows the outer execute() call and not the internal delegatecall logic, we cannot directly verify the setClaimer call inside the payload, but the target address match and the well-documented nature of this proposal (with linked source code, tests, and deployed contract addresses) support that the calldata is consistent with the described action. The described actions of the separate Retrieval Contract (claiming on behalf of the DAO and transferring to the multisig) are correctly described as being triggered later by the multisig, not as part of this governance proposal's calldata, so their absence from the decoded actions is not a discrepancy. No value, target, or scope mismatches were found between the prose and the single decoded action.
Generated by Kvorum
04Actions
- Target
- 0x9e0f…2df8
- Value
- 0 wei
- Function
- fallback()
- Arguments
{}- Calldata
05Tally
Summed from votes
06Voters
| Voter | Choice | % of total | Rationale | ||
|---|---|---|---|---|---|
| 070x0703…961b | For | 95K | 16.83% | — | 4y ago |
| DC0xdc1f…e432 | For | 95K | 16.82% | — | 4y ago |
| AF0xafda…3a6e | For | 93.4K | 16.54% | — | 4y ago |
| 620x62a4…816a | For | 86K | 15.23% | — | 4y ago |
| B80xb83b…cf5c | For | 85K | 15.05% | — | 4y ago |
| 680x683a…6c02 | For | 62.1K | 10.99% | — | 4y ago |
| B80xb8c2…4f87 | For | 19.2K | 3.40% | — | 4y ago |
| B70xb777…e1a5 | For | 10K | 1.77% | — | 4y ago |
| 210x212b…6db5 | For | 10K | 1.77% | — | 4y ago |
| 320x329c…3ed4 | For | 5.3K | 0.94% | — | 4y ago |
| 5B0x5b3b…7c98 | For | 3.3K | 0.59% | — | 4y ago |
| F70xf7b9…fe44 | For | 200 | 0.04% | — | 4y ago |
| B60xb6d8…8f54 | For | 122.3 | 0.02% | — | 4y ago |
| E50xe585…330e | For | 54.6 | 0.01% | — | 4y ago |
| DB0xdb8c…4196 | For | 20.8 | 0.00% | — | 4y ago |
| A00xa0ef…2d56 | For | 8.3 | 0.00% | — | 4y ago |
| C50xc5fc…5d3c | For | 6.3 | 0.00% | — | 4y ago |
| 000x0064…f9a3 | For | 2 | 0.00% | — | 4y ago |
| C20xc205…9274 | For | 1.4 | 0.00% | — | 4y ago |
| 520x52b6…335c | For | 1.3 | 0.00% | — | 4y ago |
| 8D0x8d4f…e608 | For | 1.2 | 0.00% | — | 4y ago |
| 140x14ff…05b8 | For | 1 | 0.00% | — | 4y ago |
| 9D0x9d11…0e53 | For | 1 | 0.00% | — | 4y ago |
| DC0xdca9…8da4 | For | 1 | 0.00% | — | 4y ago |
| 220x2249…3489 | For | 1 | 0.00% | — | 4y ago |
| 470x4702…62c9 | For | 1 | 0.00% | — | 4y ago |
| F20xf292…9747 | For | 1 | 0.00% | — | 4y ago |
| 520x5287…62dd | For | 0.9 | 0.00% | — | 4y ago |
| 0D0x0d3b…d1bc | For | 0.8 | 0.00% | — | 4y ago |
| 490x49d2…0009 | For | 0.7 | 0.00% | — | 4y ago |
| 690x6917…0b8d | For | 0.7 | 0.00% | — | 4y ago |
| 000x0069…296b | For | 0.7 | 0.00% | — | 4y ago |
| 160x16c2…7768 | For | 0.4 | 0.00% | — | 4y ago |
| F00xf063…ec45 | For | 0.4 | 0.00% | — | 4y ago |
| 5E0x5e59…2bae | For | 0.4 | 0.00% | — | 4y ago |
| 420x4295…8429 | For | 0.4 | 0.00% | — | 4y ago |
| 990x997b…618d | For | 0.3 | 0.00% | — | 4y ago |
| FF0xff93…6d59 | For | 0.3 | 0.00% | — | 4y ago |
| A50xa5fe…9906 | For | 0.3 | 0.00% | — | 4y ago |
| 220x22a6…805e | For | 0.3 | 0.00% | — | 4y ago |
| 010x0155…6639 | For | 0.2 | 0.00% | — | 4y ago |
| 0D0x0d95…2392 | For | 0.2 | 0.00% | — | 4y ago |
| 610x615b…be40 | For | 0.2 | 0.00% | — | 4y ago |
| A20xa203…b84f | For | 0.2 | 0.00% | — | 4y ago |
| 240x2487…4751 | For | 0.2 | 0.00% | — | 4y ago |
| 6A0x6ada…041f | For | 0.2 | 0.00% | — | 4y ago |
| 7F0x7f4c…cf57 | For | 0.2 | 0.00% | — | 4y ago |
| BB0xbbe1…1220 | For | 0.2 | 0.00% | — | 4y ago |
| CC0xccc2…e8d6 | For | 0.2 | 0.00% | — | 4y ago |
| C10xc1e7…f293 | For | 0.2 | 0.00% | — | 4y ago |
07Forum
- [ARC] Whitelist Balancer’s Liquidity Mining Claim ↗discourse · high confidence
- ARC - Continue Liquidity Mining Program on Aave V2 Ethereum market and Introduce Liquidity Mining on Aave ARC market ↗discourse · high confidence
Arguments for
- The proposal enables Balancer DAO to recover approximately 1,500 stkAAVE liquidity mining rewards that accrued in Linear Pools but cannot be claimed or managed by those contracts without governance intervention.— Llamaxyz, MatthewGraham, solarcurve, Gleb
Arguments against
None surfaced.
Notable participants
- LlamaxyzCo-author and proposer of the whitelisting proposal.
- MatthewGrahamCo-author and proposer of the whitelisting proposal.
- solarcurveEarly supporter who publicly thanked the proposal authors for their effort.
- GlebExpressed full agreement with the proposal.
Generated by Kvorum
08Similar proposals
- aaveexecutedAllow Balancer To Claim Mining Rewards83%
- aaveexecutedAllow Balancer DAO to Claim Liquidity Mining Rewards (Arbitrum & Base)80%
- aavecanceledAllow Balancer DAO to Claim Liquidity Mining Rewards (Arbitrum & Base)80%
- aaveexecutedClaim Aave v2 stkAAVE rewards77%
- aaveexecutedClaiming AAVE Rewards for the Sablier Legacy v1.1 Contract75%
- aaveexecutedintroduce Liquidity Incentives for Aave v273%
- aaveexecutedAdd claimRewardsToSelf() to incentives for Ethereum V2 Aave Market73%
- aaveexecutedEnhancing Aave DAO’s Liquidity Incentive Strategy on Balancer72%
- aaveexecutedAave V2 - Liquidity Mining Program (90 days at 30% reduced rate)71%
- aaveexecutedActivation of the Aave Balancer Pool Liquidity Staking70%