KVORUM
aaveSource: Aave governance v3 · #179

Aave Liquidity Committee Funding Phase IV

executedOct 8, 2024, 03:12 PM UTCby570x57ab…2922

01Summary

AISummary by Kvorumclaude-haiku-4-5

This AIP allocates 950,000 GHO tokens to the Aave Liquidity Committee (ALC) for Phase IV, which focuses on sustaining and improving GHO liquidity across Ethereum and Arbitrum networks through integrations with InstadApp, Royco, and Synthetix.

Type
treasury allocation

Key changes

  • Creation of an allowance for 950,000 GHO tokens on Ethereum to the ALC Ethereum SAFE (0xA1c93D2687f7014Aaf588c764E3Ce80aF016229b)(high)
  • Funding for GHO liquidity initiatives including InstadApp vault integration, Royco yield strategy launch, and Synthetix strataGHO perpetual market on Arbitrum(high)
  • Phase IV liquidity focus targets 50M DEX liquidity on Ethereum while maintaining current performance metrics (sub-0.10% price impact for $5M swaps, <5% peg volatility, $0.995 price level >90% of the time)(medium)
Contracts0x9ed119f4e1966b4a7e6be384d6b42bb6da9f981a
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

317 words

Simple Summary

Upon implementation, this AIP will make available 950,000 GHO to the Aave Liquidity Committee (ALC).

Motivation

Phase IV of the ALC focuses on sustaining and improving GHO liquidity across the Ethereum and Arbitrum networks, while also encouraging broader adoption of GHO through various integrations with other protocols.

In the near future, we expect GHO to be listed on InstadApp, with several curated vaults providing additional utility and yield opportunities for GHO.

GHO is also expected to feature in the upcoming Royco launch, aimed at driving flows into several yield strategies across Ethereum and Arbitrum.

We anticipate achieving the first perpetual market integration for GHO with a strataGHO listing on Synthetix on Arbitrum.

Each integration is expected to provide a use case that strengthens GHO's on-chain liquidity.

The table below presents the performance metrics for the ALC.

DescriptionEthereum ValueArbitrum Value
TVL DEX Liquidity Pools50M30M
TVL Utility Liquidity Pools (Excl. stkGHO)15M10M
DEX Liquidity Composition< 50% GHO (< 33% for 3pools)< 50% GHO (< 33% for 3pools)
Swap Price Impact $5M Swap (GHO to USDC)< 0.10%< 0.25%
Annualised Peg Volatility< 5.00%< 5.00%
Price level for >90% time$0.995 using Redstone Medium Price$0.995 using Redstone Medium Price

Achieving 50M of DEX liquidity on Ethereum across various integrations remains a key focus. Whilst we are yet to acheive this target, we are currently very well positioned for current market conditions.

Specification

Create an Allowance for GHO on Ethereum for a total of 950,000 GHO.

ALC Ethereum SAFE: 0xA1c93D2687f7014Aaf588c764E3Ce80aF016229b

References

Copyright

Copyright and related rights waived via CC0.

03Mismatch analysis

AIMismatch analysis by Kvorumlow confidenceclaude-sonnet-5
Consistent

The proposal follows the standard Aave governance execution pattern: the on-chain action is a single call to execute() on a payload contract, which is delegatecalled by the governance executor. The decoded calldata does not expose the internal logic of that payload contract (e.g., the actual GHO.approve/allowance call, the amount, or the recipient Safe address), so it is not possible to directly verify the specific figures (950,000 GHO, ALC Ethereum SAFE address) claimed in the description against the raw decoded action. This is typical for Aave AIPs, where the real specification lives in the linked Solidity implementation file rather than in the top-level calldata. Because the calldata itself contains no arguments or sub-calls to compare against the prose, I cannot confirm or refute the specific amount or recipient claims, and no other omissions, extra actions, or mismatched targets are visible at this level of decoding. Given this opacity, confidence in the comparison is low, and no discrepancy is flagged since none can be substantiated from the available decoded data. Delegates relying solely on this decoded action list would need to inspect the underlying payload contract source to fully verify the amount and recipient match the description exactly.

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
0x9ed1…981a
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.