KVORUM
aaveSource: Aave governor v2 · #12

Whitelist Curve Liquidity Mining Claim

executedMay 7, 2021, 01:39 PM UTCbyA70xa749…c3cc

01Summary

AISummary by Kvorumclaude-haiku-4-5

Enable Curve Finance contracts to claim StkAAVE rewards on behalf of users depositing into Aave pools, strengthening the synergy between Aave and Curve following the liquidity mining program launched in AIP-16.

Type
protocol addition

Key changes

  • Set Curve aPool contract (0x96D7BC17912e4F320c4894194564CF8425cfe8d9) as claimer for rewards token 0xDeBF20617708857ebe4F679508E7b7863a8A8EeE on the Incentives Controller(medium)
  • Set Curve sPool contract (0xe5f41aCAd47849C6eb28b93913ca81893fB5a2A6) as claimer for rewards token 0xEB16Ae0052ed37f479f7fe63849198Df1765a733 on the Incentives Controller(medium)
Contracts0xd784927ff2f95ba542bfc824c8a8a98f3495f6b50x96D7BC17912e4F320c4894194564CF8425cfe8d90xe5f41aCAd47849C6eb28b93913ca81893fB5a2A6
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

181 words

AIP rationale

With the results of AIP-16, A liquidity mining program started on the Aave V2 protocol.

Many protocol took this opportunity to reinforce their synergies with Aave and deposit liquidity on Aave on behalf of their users.

For some protocols based on immutable contracts, participating in the Liquidity mining program requires some slight governance intervention on both sides.

Curve.finance is one of them, they implemented via a community work the compability with the Aave liquidity for their Aave and sAave pools : https://dao.curve.fi/vote/ownership/45

It's now up to the Aave community to strengthten this synergy on Aave side allowing Curve users depositing into Aave to collect both CRV & StkAAVE rewards.

AIP content in short

  • Set Curve contract as claimers in the incentives controller contract.

Relevant Links

Implementations details

call setClaimer() for Curve contracts on INCENTIVES_CONTROLLER_PROXY_ADDRESS

Curve aPool contract : https://etherscan.io/address/0x96D7BC17912e4F320c4894194564CF8425cfe8d9

Curve sPool contract : https://etherscan.io/address/0xe5f41acad47849c6eb28b93913ca81893fb5a2a6

Link to incentives controller proxy : https://etherscan.io/address/0xd784927Ff2f95ba542BfC824c8a8a98F3495f6b5#readProxyContract

Copyright

Copyright and related rights waived via CC0.

03Mismatch analysis

AIMismatch analysis by Kvorummedium confidenceclaude-sonnet-5
Consistent

The description states the AIP will set Curve's aPool and sPool contracts as claimers in Aave's Incentives Controller, linking to the exact contract addresses used in the implementation details. Both decoded calldata actions target the same Incentives Controller proxy address (0xd784927Ff2f95ba542BfC824c8a8a98F3495f6b5) referenced in the description, and the second argument of each setClaimer call exactly matches the Curve aPool and sPool addresses cited in the description (case differences are immaterial). The first argument in each call (the 'user' address whose rewards Curve is authorized to claim) is not explicitly named in the prose, but this is a routine implementation detail (the specific aToken/user being tied to the Curve claimer) consistent with the stated goal of enabling Curve to claim on behalf of depositors - this is a legitimate summarization, not an omission of a materially different action. No value transfers, unexpected targets, or parameter mismatches were found. Confidence is medium rather than high only because the exact identity/purpose of the 'user' addresses (0xDeBF20... and 0xEB16Ae...) could not be independently verified from the text alone, though their role is a standard and expected part of the setClaimer mechanism described.

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
#0setClaimer(address,address)chain 0x1
Target
0xd784…f6b5
Value
0 wei
Function
setClaimer(address,address)
Arguments
{
  "0": "0xDeBF20617708857ebe4F679508E7b7863a8A8EeE",
  "1": "0x96D7BC17912e4F320c4894194564CF8425cfe8d9"
}
Calldata
#1setClaimer(address,address)chain 0x1
Target
0xd784…f6b5
Value
0 wei
Function
setClaimer(address,address)
Arguments
{
  "0": "0xEB16Ae0052ed37f479f7fe63849198Df1765a733",
  "1": "0xe5f41aCAd47849C6eb28b93913ca81893fB5a2A6"
}
Calldata

05Tally

Summed from votes

Voters47
VP participating411.7K
Outcome (current)For
Current support100%

06Voters

47 total
Filter:
VoterChoice% of totalRationale
C40xc4a9…2935For92.5K22.47%—6y ago
360x36c4…2a8aFor78.3K19.03%—6y ago
5B0x5bc9…d76cFor76.3K18.54%—6y ago
A30xa3f0…b233For63.6K15.45%—6y ago
700x704d…a0dfFor50.1K12.17%—6y ago
800x80dc…c146For27.4K6.64%—6y ago
460x46ab…b4d1For7.7K1.87%—6y ago
510x510b…9938For4.8K1.17%—6y ago
970x9757…e331For4K0.97%—6y ago
A50xa550…668fFor1.1K0.28%—6y ago
F70xf7ea…938cFor1K0.24%—6y ago
A70xa749…c3ccFor604.20.15%—6y ago
C30xc3ff…1d22For600.50.15%—6y ago
800x80ee…e12eFor548.40.13%—6y ago
CA0xca76…6f46For5250.13%—6y ago
3E0x3e33…bbf7For4000.10%—6y ago
4A0x4ada…1c6bFor333.50.08%—6y ago
720x72b2…cfb3For295.70.07%—6y ago
B30xb35a…7aeeFor2770.07%—6y ago
930x93d9…a883For194.80.05%—6y ago
E00xe079…98d6For189.60.05%—6y ago
ED0xed57…c23aFor176.30.04%—6y ago
2A0x2ae1…86d6For175.50.04%—6y ago
600x6001…887aFor112.60.03%—6y ago
7F0x7f18…caedFor720.02%—6y ago
8D0x8d07…a265For500.01%—6y ago
750x7553…584fFor33.90.01%—6y ago
540x54e5…324aFor29.80.01%—6y ago
A40xa400…e5f6For28.40.01%—6y ago
DF0xdf8a…21caFor27.90.01%—6y ago
6B0x6bac…342cFor210.01%—6y ago
0A0x0a53…dd2eFor16.80.00%—6y ago
2A0x2ad7…f5c6For13.40.00%—6y ago
ED0xedb7…4f57For10.10.00%—6y ago
7B0x7bb2…fa0eFor6.70.00%—6y ago
3F0x3fbd…ded9For5.10.00%—6y ago
320x32ca…c384For4.10.00%—6y ago
1D0x1d5e…69f4For2.90.00%—6y ago
100x10f4…780dFor2.90.00%—6y ago
490x4908…59b9For20.00%—6y ago
FF0xffd7…f957For1.40.00%—6y ago
800x8042…4379For1.30.00%—6y ago
610x610c…f2e0For10.00%—6y ago
770x7785…cd08For10.00%—6y ago
A10xa1c7…f483For0.90.00%—6y ago
4A0x4a5e…95dcFor0.10.00%—6y ago
DB0xdb2b…d15bFor00.00%—6y ago
Showing 47

07Forum

No forum thread is confidently linked to this proposal.