KVORUM
aaveSource: Aave governance v3 · #387

Claim Aave v2 stkAAVE rewards

executedOct 7, 2025, 12:02 PM UTCbyF70xf71f…1e02

01Summary

AISummary by Kvorumclaude-haiku-4-5

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
ContractsEthereum V2 Incentives ControllerAave CollectorGovernance V2 Short ExecutorGovernance V3 Lvl 1 Executor
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

212 words

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

Copyright

Copyright and related rights waived via CC0.

03Mismatch analysis

AIMismatch analysis by Kvorummedium confidenceclaude-sonnet-5
Consistent

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
model: claude-sonnet-5
provider: anthropic
profile: anthropic-strong-v1
prompt: v1.0
generated: 2mo ago
Review the decoded actions ↗

04Actions

2 total
#0fallback()chain 0x1
Target
0x95d9…f90f
Value
0 wei
Function
fallback()
Arguments
{}
Calldata
#0fallback()chain 0x1
Target
0xd6ff…c48f
Value
0 wei
Function
fallback()
Arguments
{}
Calldata

05Tally

Summed from votes

Voters29
VP participating888.1K
Outcome (current)For
Current support100%

06Voters

29 total
Filter:
VoterChoice% of totalRationale
EA0xea0c…6b5aFor333K37.50%—1y ago
570x57ab…2922For279.2K31.44%—1y ago
EZezr3al.eth0x8659…7d0eFor136.2K15.34%—1y ago
B90xb933…8dd1For39.6K4.46%—1y ago
EC0xecc2…6ac9For26K2.93%—1y ago
870x8787…ea52For25.7K2.89%—1y ago
3D0x3ddc…05b0For20.1K2.27%—1y ago
8B0x8b37…2a22For10.3K1.16%—1y ago
3E0x3e32…c4d0For7.7K0.86%—1y ago
2C0x2cc1…4df1For6.7K0.75%—1y ago
0E0x0e00…ccfcFor1.1K0.12%—1y ago
440x4444…34b3For6820.08%—1y ago
B30xb356…c826For4800.05%—1y ago
4D0x4d26…7017For397.40.04%—1y ago
A50xa54f…0f31For264.20.03%—1y ago
CA0xcafc…1544For259.70.03%—1y ago
F10xf13c…6dd3For236.30.03%—1y ago
080x0865…24ceFor149.40.02%—1y ago
270x2748…ac26For16.10.00%—1y ago
430x43dd…40e0For7.90.00%—1y ago
F70xf7fb…dc1aFor60.00%—1y ago
7E0x7e6c…73ebFor5.60.00%—1y ago
BB0xbb86…3527For4.80.00%—1y ago
010x010d…4ee4For1.30.00%—1y ago
010x019e…2ee3For0.30.00%—1y ago
010x0100…7cc9For0.20.00%—1y ago
160x168f…7400For0.10.00%—1y ago
2F0x2f2f…f78aFor00.00%—1y ago
4D0x4d4a…1bdfFor00.00%—1y ago
Showing 29

07Forum

No forum thread is confidently linked to this proposal.