KVORUM
aaveSource: Aave governance v3 · #176

Set ACI as Emission Manager for USDS, aUSDS and awstETH

executedOct 6, 2024, 03:38 PM UTCby570x57ab…2922

01Summary

AISummary by Kvorumclaude-haiku-4-5

Appoint Aave-Chan Initiative (ACI) as the Emission Manager for USDS, aUSDS, and awstETH on Aave Ethereum to manage liquidity mining programs and incentives for suppliers.

Type
governance change

Key changes

  • Set ACI multisig address (0xac140648435d03f784879cd789130F22Ef588Fcd) as emission admin for USDS and aUSDS via setEmissionAdmin() method(high)
  • Enable ACI to manage liquidity mining programs for USDS suppliers on Aave(high)
  • Allow wstETH suppliers on Lido instance to receive incentives aligned with the Ahab Program(medium)

Notable concerns

  • Proposal depends on AIP-175 execution to allow aEthUSDS and aEthLidoUSDS creation
Contracts0xdC035D45d973E3EC169d2276DDab16f1e407384F0x32a6268f9Ba3642Dda7892aDd74f1D34469A42590x09AA30b182488f769a9824F15E6Ce58591Da47810x223d844fc4B006D67c0cDbd39371A9F73f69d974
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

194 words

Simple Summary

This AIP proposes to appoint the Aave-Chan Initiative (ACI) as the Emission Manager for USDS, aUSDS and awstETH on Aave Ethereum Main & Lido instances.

Motivation

Liquidity mining programs are essential for attracting liquidity providers by offering rewards for their participation. Effective management of these programs is crucial for the sustained growth of the Aave Ecosystem. Therefore, with its extensive experience and strategic partnerships, ACI is well-positioned to manage these emissions effectively.

To support Aave & Sky ecosystem synergies, The ACI will manage liquidity mining programs for USDS suppliers on Aave.

This proposal also seeks to allow wstETH suppliers on the lido instance to receive incentives in line with the Ahab Program

Specification

The ACI multisig address will be set as the emission manager via the setEmissionAdmin() method in the relevant emission manager contracts for USDS & aUSDS.

ACI multisig address: 0xac140648435d03f784879cd789130F22Ef588Fcd USDS: 0xdC035D45d973E3EC169d2276DDab16f1e407384F aEthUSDS*: 0x32a6268f9Ba3642Dda7892aDd74f1D34469A4259 aEthLidoUSDS*: 0x09AA30b182488f769a9824F15E6Ce58591Da4781 Aave Emission Manager contract on Ethereum: 0x223d844fc4B006D67c0cDbd39371A9F73f69d974

  • This payload requires the AIP-175 to be executed to allow aEthUSDS & aEthLidoUSDS creation

References

Copyright

Copyright and related rights waived via CC0.

03Mismatch analysis

AIMismatch analysis by Kvorumlow confidenceclaude-sonnet-5
Consistent

The decoded on-chain action set contains only a single generic execute() call to a payload contract, with no decoded internal arguments or sub-calls. This is the standard pattern for Aave governance proposals: the top-level governance action is always a call to a pre-audited payload contract's execute() function, and the actual logic (here, the three setEmissionAdmin() calls to the USDS, aUSDS, and awstETH emission managers naming the ACI multisig) is encoded inside that payload contract's bytecode, not visible in this decoded calldata. Because the payload address matches the proposal's linked implementation/test files referenced in the description, and no additional or conflicting top-level actions are present, there is no evidence of a mismatch between the prose and what will execute. However, since the decoded calldata does not expose the specific addresses, function calls, or parameters described in the prose (e.g., the exact setEmissionAdmin target contracts and the ACI multisig address), a reviewer cannot fully verify claim-by-claim accuracy from this data alone. I am marking confidence as low rather than flagging any discrepancy, since the opacity is due to the standard payload-execution pattern rather than any indication of an intentional mismatch.」,

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
0x08af…4091
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.