KVORUM
aaveSource: Aave governance v3 · #91

stkGHO Incentives

executedApr 30, 2024, 09:28 PM UTCby570x57ab…2922

01Summary

AISummary by Kvorumclaude-haiku-4-5

Re-enable AAVE emissions to stkGHO holders at 100 AAVE per day for 180 days to support the GHO stablecoin peg and enable future GHO supply expansion.

Type
parameter change

Key changes

  • Set stkGHO daily AAVE emission allowance to 100 AAVE per day(high)
  • Set distribution period for 180 days from execution date(high)
Contracts0xe30ef3c5acac776b5e0ac6e7e103f9b5f81e06ae
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

90 words

Simple Summary

Re-enable stkGHO incentives emissions for 180 days after previous period ended.

Motivation

To support the GHO peg and to pave the way for future GHO supply expansion, this publication proposes maintaining the daily AAVE emission going to stkGHO holders.

Specification

For stkGHO:

  • Set new allowance to 100 AAVE per day for 180 days
  • Set distribution end for 180 days from Execution date

References

Copyright

Copyright and related rights waived via CC0.

03Mismatch analysis

AIMismatch analysis by Kvorumlow confidenceclaude-sonnet-5
Consistent

The proposal follows Aave's standard governance pattern: the on-chain action is a single execute() call to a payload contract address, which is typical for Aave V3 proposals (the referenced implementation .sol file shows the payload logic including AaveV3Ethereum.COLLECTOR/STK_AAVE calls setting emission per second and distribution end). The decoded calldata here only shows the generic execute() fallback with no arguments, meaning the specific numeric details (100 AAVE/day, 180-day distribution end) cannot be independently verified from this decoded action alone — they live inside the payload contract's bytecode referenced by the description's GitHub link. Since there is no way to cross-check the exact emission rate or duration against the calldata provided, confidence is low. However, nothing in the calldata contradicts the description, and the pattern (single execute() call to a named payload) is exactly what would be expected for this type of proposal, so no discrepancy is flagged — only that verification is limited by the shallow decoding depth (top-level execute() rather than internal calls).

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
0xe30e…06ae
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.