KVORUM
aaveSource: Aave governance v3 · #243

Allow Balancer To Claim Mining Rewards

executedFeb 9, 2025, 10:58 PM UTCby570x57ab…2922

01Summary

AISummary by Kvorumclaude-haiku-4-5

This Aave governance proposal authorizes the Balancer DAO to claim liquidity mining rewards generated by Balancer v3 Boosted Pools deposited in Aave Protocol. It designates a specific Balancer contract (0x9ff471F9f98F42E5151C7855fD1b5aa906b1AF7e) as the claimer for rewards on behalf of the Balancer v3 vault (0xbA1333333333a1BA1108E8412f11850A5C319bA9) on both Ethereum and Gnosis Chain.

Type
governance change

Key changes

  • Authorize contract 0x9ff471F9f98F42E5151C7855fD1b5aa906b1AF7e as claimer for liquidity mining rewards on behalf of Balancer v3 vault on Ethereum Core(high)
  • Authorize contract 0x9ff471F9f98F42E5151C7855fD1b5aa906b1AF7e as claimer for liquidity mining rewards on behalf of Balancer v3 vault on Gnosis Chain(high)
  • Enable Balancer DAO to retrieve and redistribute Aave liquidity mining rewards from Boosted Pools to users and the DAO(high)
Contracts0x77051aeb284d0a1c06c02082c4156f185dadb08e0x9ff471F9f98F42E5151C7855fD1b5aa906b1AF7e0xbA1333333333a1BA1108E8412f11850A5C319bA9
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

175 words

Simple Summary

This publication proposes allowing the Balancer DAO to claim liquidity mining rewards generated by Balancer v3 Boosted Pools through the Aave Protocol.

Motivation

With the launch of Balancer v3, the new Boosted Pool type allocates some or all tokens to generate additional yield for liquidity providers, primarily through deposits into the Aave Protocol. Yield-bearing tokens can comprise 25% to 100% of a Boosted Pool's total liquidity.

This proposal enables the Balancer DAO to retrieve liquidity mining rewards from Boosted Pools for redistribution to users and the DAO.

To facilitate this, Aave Protocol’s claimOnBehalfOf function allows designated addresses to claim rewards on behalf of smart contracts.

Without assigning a specific address as the contract owner, these rewards cannot be claimed, leaving them inaccessible.

Specification

Set Balancer contract 0x9ff471F9f98F42E5151C7855fD1b5aa906b1AF7e as the claimer (caller) on behalf of the Balancer v3 vault as the user 0xbA1333333333a1BA1108E8412f11850A5C319bA9, on both Ethereum Core and Gnosis.

References

Copyright

Copyright and related rights waived via CC0.

03Mismatch analysis

AIMismatch analysis by Kvorumlow confidenceclaude-sonnet-5
Consistent

The proposal describes a specific, narrow action: authorizing a Balancer contract as claimer of Aave liquidity mining rewards on behalf of the Balancer v3 vault, on both Ethereum and Gnosis. The only decoded on-chain action is a generic execute() (fallback) call to a payload executor contract on Ethereum, with no decoded arguments. This is the standard pattern used by Aave governance proposals, where the executor contract internally delegatecalls into a payload implementation (matching the linked AaveV3Multi implementation contract) that performs the actual setClaimer-type logic and dispatches any necessary cross-chain message to Gnosis. Because the decoded calldata provides no argument-level detail, it is not possible to directly confirm the specific addresses (claimer, vault) or the Gnosis-side action from the calldata alone — this drives confidence down to 'low'. However, nothing in the decoded action contradicts the description, and the pattern (single opaque execute() call implementing a documented external payload) is routine and expected for this proposal type, so no severe or material issue is flagged. The main note is that the Gnosis leg of the action is not independently visible in the decoded action list, which is flagged as a low-severity omission for transparency, but is not indicative of malicious or materially different behavior.

Discrepancies

  • lowomitted in description

    The description explicitly states the claimer permission will be set on both Ethereum Core and Gnosis, but the decoded on-chain action list only contains a single execute() call targeting Ethereum (chain 0x1). There is no separate decoded action for Gnosis. This is consistent with Aave's typical cross-chain governance pattern (the Ethereum execute() call can trigger a bridged message to Gnosis internally), but it cannot be independently verified from the opaque fallback call alone.

    “on both Ethereum Core and Gnosis”

Generated by Kvorum
model: claude-sonnet-5
provider: anthropic
profile: anthropic-strong-v1
prompt: v1.0
generated: 2mo ago
Review the decoded actions ↗

04Actions

1 total
#0fallback()chain 0x1
Target
0x7705…b08e
Value
0 wei
Function
fallback()
Arguments
{}
Calldata

05Tally

Summed from votes

Voters0
VP participating0
Outcome (current)—
Current support—

06Voters

0 total

No votes recorded yet.

07Forum

No forum thread is confidently linked to this proposal.