Claim Aave v2 stkAAVE rewards
01Summary
Claim approximately 560 unclaimed StkAave tokens (worth ~$150,000) from the Ethereum V2 Incentives Controller and transfer them to the Aave Collector for proper treasury management. This requires two payload contracts to work through the legacy Aave V2 Governance structure.
- Type
- treasury allocation
- Funding
- $~150,000
Key changes
- Authorize executor address as claimer on Ethereum V2 Incentives Controller via setClaimer()(medium)
- Claim all pending StkAave rewards (~560 tokens) and transfer to Aave Collector(high)
- Queue and execute transaction through Governance V2 Short Executor to access EMISSIONS_ADMIN role(medium)
Notable concerns
- Requires coordination between Governance V3 and legacy Governance V2 systems
- Two-part payload execution needed due to EMISSIONS_ADMIN role residing in legacy executor
Generated by Kvorum
02Description
Simple Summary
Maintenance proposal to claim unclaimed StkAave rewards from the Ethereum V2 Incentives Controller.
Motivation
During routine treasury analysis, TokenLogic identified approximately 560 StkAave tokens (around $150,000 at current market prices) sitting unclaimed in the Ethereum V2 Incentives Controller contract. These dormant rewards represent treasury assets that should be actively managed rather than left idle, making it prudent for the DAO to claim and transfer them to the Aave Collector for proper treasury optimization.
Specification
To claim the unclaimed StkAave reward, the payload:
- Sets Claimer Authorization: Calls
setClaimer()on the Ethereum V2 Incentives Controller to authorize the executor address as the claimer. - Executes Claim: Calls
claimRewardsOnBehalf()to claim all pending StkAave rewards and transfer them directly to the Aave Collector.
Since the EMISSIONS_ADMIN role resides with the legacy Aave V2 Governance Short Executor, the implementation requires two additional payload contracts on Ethereum, to be called by the Governance V3 Lvl 1 Executor:
- PART 1 Queue Payload: Contract calling
queueTransaction()to queue the execution on Governance V2 Short Executor - PART 2 Execute Payload: Contract calling
executeTransaction()to execute the queued transaction via Governance V2 Short Executor
References
- Implementation: AaveV2Ethereum
- Tests: AaveV2Ethereum
- Discussion
Copyright
Copyright and related rights waived via CC0.
03Mismatch analysis
The proposal describes a two-part Aave V2/V3 governance payload architecture: a 'Queue Payload' contract that calls queueTransaction() on the legacy Short Executor, and an 'Execute Payload' contract that calls executeTransaction() to trigger setClaimer() and claimRewardsOnBehalf(), ultimately routing unclaimed StkAave rewards to the Aave Collector. The decoded on-chain actions show exactly two top-level calls, each invoking execute() (via fallback) on distinct contract addresses — matching the expected pattern of calling PART 1 and PART 2 payload contracts from the Governance V3 Lvl 1 Executor. Because Aave governance proposals commonly execute via a single execute() entrypoint on payload contracts whose internal logic (setClaimer, claimRewardsOnBehalf, queueTransaction, executeTransaction) is not separately decoded at the top level, the absence of these calls in the decoded action list is expected and not indicative of a mismatch. No value transfers, target mismatches, or magnitude discrepancies are apparent. Confidence is medium rather than high because the decoded calldata does not expose the internal call chain, so full verification of the specific claimer/collector addresses is not possible from this data alone, though the described architecture is a well-known, standard pattern for this type of maintenance proposal.
Discrepancies
- lowomitted in description
The decoded calldata only shows two top-level execute() calls to payload contracts; the specific internal calls (setClaimer, claimRewardsOnBehalf, queueTransaction, executeTransaction) described in the prose are not directly visible in the decoded top-level actions. This is typical for Aave governance payload proposals where deeper logic resides in linked payload contract source code, so it is not treated as a material discrepancy, but reviewers should note that verification of the exact internal claim/queue logic relies on the linked source rather than the decoded calldata alone.
Generated by Kvorum
04Actions
- Target
- 0x95d9…f90f
- Value
- 0 wei
- Function
- fallback()
- Arguments
{}- Calldata
- Target
- 0xd6ff…c48f
- Value
- 0 wei
- Function
- fallback()
- Arguments
{}- Calldata
05Tally
Summed from votes
06Voters
| Voter | Choice | % of total | Rationale | ||
|---|---|---|---|---|---|
| EA0xea0c…6b5a | For | 333K | 37.50% | — | 1y ago |
| 570x57ab…2922 | For | 279.2K | 31.44% | — | 1y ago |
| EZezr3al.eth0x8659…7d0e | For | 136.2K | 15.34% | — | 1y ago |
| B90xb933…8dd1 | For | 39.6K | 4.46% | — | 1y ago |
| EC0xecc2…6ac9 | For | 26K | 2.93% | — | 1y ago |
| 870x8787…ea52 | For | 25.7K | 2.89% | — | 1y ago |
| 3D0x3ddc…05b0 | For | 20.1K | 2.27% | — | 1y ago |
| 8B0x8b37…2a22 | For | 10.3K | 1.16% | — | 1y ago |
| 3E0x3e32…c4d0 | For | 7.7K | 0.86% | — | 1y ago |
| 2C0x2cc1…4df1 | For | 6.7K | 0.75% | — | 1y ago |
| 0E0x0e00…ccfc | For | 1.1K | 0.12% | — | 1y ago |
| 440x4444…34b3 | For | 682 | 0.08% | — | 1y ago |
| B30xb356…c826 | For | 480 | 0.05% | — | 1y ago |
| 4D0x4d26…7017 | For | 397.4 | 0.04% | — | 1y ago |
| A50xa54f…0f31 | For | 264.2 | 0.03% | — | 1y ago |
| CA0xcafc…1544 | For | 259.7 | 0.03% | — | 1y ago |
| F10xf13c…6dd3 | For | 236.3 | 0.03% | — | 1y ago |
| 080x0865…24ce | For | 149.4 | 0.02% | — | 1y ago |
| 270x2748…ac26 | For | 16.1 | 0.00% | — | 1y ago |
| 430x43dd…40e0 | For | 7.9 | 0.00% | — | 1y ago |
| F70xf7fb…dc1a | For | 6 | 0.00% | — | 1y ago |
| 7E0x7e6c…73eb | For | 5.6 | 0.00% | — | 1y ago |
| BB0xbb86…3527 | For | 4.8 | 0.00% | — | 1y ago |
| 010x010d…4ee4 | For | 1.3 | 0.00% | — | 1y ago |
| 010x019e…2ee3 | For | 0.3 | 0.00% | — | 1y ago |
| 010x0100…7cc9 | For | 0.2 | 0.00% | — | 1y ago |
| 160x168f…7400 | For | 0.1 | 0.00% | — | 1y ago |
| 2F0x2f2f…f78a | For | 0 | 0.00% | — | 1y ago |
| 4D0x4d4a…1bdf | For | 0 | 0.00% | — | 1y ago |
07Forum
No forum thread is confidently linked to this proposal.
08Similar proposals
- aaveexecutedClaiming AAVE Rewards for the Sablier Legacy v1.1 Contract77%
- aaveexecutedWhitelist Balancer’s Liquidity Mining Claim77%
- aaveexecutedAdd claimRewardsToSelf() to incentives for Ethereum V2 Aave Market76%
- aaveexecutedintroduce Liquidity Incentives for Aave v270%
- aaveexecutedAllow Balancer To Claim Mining Rewards67%
- aaveexecutedAave V2 - Liquidity Mining Update (90 days at 30% reduced rate)66%
- aaveexecutedWhitelist Curve Liquidity Mining Claim65%
- aaveexecutedAave V2 - Liquidity Mining Program (90 days at 30% reduced rate)65%
- aaveexecutedActivation of the Aave Balancer Pool Liquidity Staking64%
- aaveexecutedwstETH CAPO Oracle Incident User Reimbursement64%