KVORUM
aaveSource: Aave governance v3 · #296

Aave Liquidity Committee Funding Phase VI

executedApr 20, 2025, 08:18 PM UTCby570x57ab…2922

01Summary

AISummary by Kvorumclaude-haiku-4-5

The Aave Liquidity Committee (ALC) requests approval to withdraw 3,500,000 aEthLidoGHO tokens from the Ethereum collector to fund Phase VI activities. Phase VI focuses on expanding GHO stablecoin adoption across multiple chains (Sonic, Avalanche, Gnosis) while maintaining liquidity on Ethereum, with strategic integrations across DeFi protocols and implementation of cross-chain GSM infrastructure.

Type
treasury allocation

Key changes

  • Withdraw 3,500,000 aEthLidoGHO from Ethereum collector to ALC Ethereum SAFE (0xA1c93D2687f7014Aaf588c764E3Ce80aF016229b) for Phase VI operations(high)
  • Expand GHO deployment to Sonic, Avalanche, and Gnosis chains with tailored integrations for each ecosystem(high)
  • Implement stataGSM (modified Stability Modules) across destination chains to enable native GHO swaps and eliminate bridging friction(high)
  • Continue Ethereum mainnet GHO liquidity management across DEXs (Balancer, Curve, Maverick, Fluid) and lending protocols (Gearbox, Fluid)(medium)
  • Pursue strategic ecosystem collaborations (similar to successful Resolv model) to maximize capital efficiency and ROI on incentive spending(medium)

Notable concerns

  • GHO growth on Arbitrum remains modest due to delayed strategic integrations (Synthetix shifted focus to Base)
  • Phase VI success depends on external factors beyond ALC control per stated performance metrics
  • New chain deployments (Sonic, Avalanche, Gnosis) carry execution risks and ecosystem adoption uncertainties
  • Multichain GSM strategy effectiveness depends on successful implementation and review completion by TokenLogic and AaveLabs
Contracts0x183f144a87586dfe089d9bae5f24a799fdb7a6040xA1c93D2687f7014Aaf588c764E3Ce80aF016229b
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

1,577 words

Simple Summary

This publication presents the Aave Liquidity Committee (ALC) Phase VI Funding request.

Motivation

Phase V Update

GHO Supply

Over the course of the last quarter, the market dynamics surrounding GHO experienced a notable shift. As yield opportunities in the broader DeFi landscape became less attractive due to declining funding rates, users began redirecting their capital in search of alternative sources of return.

GHO, particularly through its liquidity provision use cases, emerged as a compelling destination. This resurgence in interest was further reinforced by the reactivation and full replenishment of the GSMs, which had previously been nearly emptied. These modules went from holding negligible balances to over $28M in total during the period.

Screenshot 2025-04-03 at 20.01.51

Ethereum

DEX Liquidity

On Ethereum, GHO's peg has been resilient and consistent during Q1 of 2025 and the deeper DEX liquidity has enabled larger swap sizes to be processed with minimal price impact.

With perp funding rates and broader DeFi liquidity costs trending lower, Liquidity Provider (LPs) deposits across GHO DEX pools experienced significant growth, surpassing $85M.

Screenshot 2025-04-03 at 19.28.53

In addition, USDT volatility helped grow GSM TVL to over $28M, ensuring continuous, on-demand support for GHO's peg.

Screenshot 2025-04-03 at 19.37.44

Balancer v3

GHO became the centerpiece asset within the new generation of Balancer pools, reflecting its growing systemic importance. On Ethereum, the primary GHO 3pool successfully migrated to the v3 boosted model, is approaching $30M in TVL.

The new Aave Boosted 3pool has exceeded the previous v2 pool’s performance, whilst also delivering superior capital efficiency and deeper liquidity provisioning. On Arbitrum liquidity was migrated from v2 to v3 liquidity and new v3 pools created on Base.

On Arbitrum and Base, these pools incorporated the new “surge” pricing mechanism, which dynamically increases swap fees as the pool diverges from the peg. This mechanism adds an additional layer of price defense, reinforcing the GHO's peg on L2s.

Screenshot 2025-04-03 at 19.43.34

Prime Instance

Another major milestone during Phase V was the introduction of the GHO and the Gho Mint facilitator on the Prime instance. This new market brought new multifaceted utility to GHO.

  • Created a structure in which GHO could be pre-minted and held by the DAO, providing operational flexibility and improving responsiveness to market demand.
  • Enables GHO to earn yield directly through variable-rate borrow mechanisms, enabling more capital-efficient stablecoin management.
  • Unlocked additional yield opportunities for Balancer v3 pools to deposit into, incentivizing further liquidity provisioning.

Lastly, the Prime instance permitted a portion of the GHO allowances allocated to service providers and ecosystem initiatives to be deposited into yield-bearing positions, improving overall capital efficiency of the assets held in the DAO's treasury.

Screenshot 2025-04-03 at 19.46.58

Fluid and Rings Integration

Fluid has been whitelisted to be the home of GHO from the backing of scUSD. It has grown to over 6M without incentive on Fluid directly with a very low acquisition cost due to a deposit campaign featuring Bungee to encourage GHO deposits in Rings.

Over the coming weeks, Rings is expected to onboard Gearbox by Veda. As GHO deposits continue to grow, GHO liquidity is expected to be distributed across Fluid and Gearbox.

Reference: https://x.com/Token_Logic/status/1905352281027166589

PYUSD/GHO Liquidity

7.5M liquidity was sourced for the PYUSD/GHO Balancer v3 liquidity pool.

Resolv Collaboration

One of the most innovative integrations of the quarter was GHO’s entry into the Resolv ecosystem. In collaboration with Resolv, the ALC deployed a campaign centered on the Curve GHO/USR LP token, and worked with both Pendle and Spectra to create yield markets enabling the ALC to receive a higher ROI on bribe spend, ~x2.2-2.4 multiplier compared to x1.1-1.3 directly on DEXs.

This was a great success knowing that no other asset of its kind had previously gained such traction in structured yield products. The campaign was enhanced by a one-month point-boost from Resolv, supplemented by strategic incentives from the ALC. The result was unprecedented: the initiative led to the formation of the largest GHO and USR liquidity pools, reaching up to $35 million in TVL.

Screenshot 2025-04-03 at 19.48.37

Arbitrum

Despite the broader success seen on Ethereum and Base, GHO’s growth on Arbitrum remains modest. The lack of meaningful traction can be attributed to delays in strategic integrations, most notably the anticipated collaboration with Synthetix, which ultimately opted to shift its primary focus and development efforts to the Base network. As a result, the GHO ecosystem on Arbitrum has yet to reach critical mass, although foundational infrastructure remains in place for future expansion.

Base

Phase V also saw the deployment of GHO on Base, a move that has already begun to bear fruit. GHO’s main liquidity pool on Base, the Balancer v3 GHO/USDC pool, has surpassed $13.5 million in TVL within a relatively short period. This rapid growth reflects strong initial interest and suggests high potential for deeper integrations. One such opportunity lies in the upcoming collaboration with Synthetix, which is now in advanced planning stages with Odos soon to integrate the stataToken factory enabling the waBasGHO integration to advance with Synthetixs.

Phase VI Lookahead

Ethereum

GHO has already secured a strong presence on Ethereum mainnet, with integrations across a wide range of protocols. It is now actively used within lending protocols such as Gearbox and Fluid, offering users capital-efficient strategies centered on GHO. In the DEX landscape, GHO is supported across Balancer, Curve, Maverick, and Fluid, demonstrating its growing utility and liquidity footprint across various automated market makers.

GHO will remain at the front stage of Ethereum's DeFi, ALC members are actively looking for collaboration with promising projects at early stage to give access to interesting opportunities for GHO holders. The latest best example was the Resolv collaboration. This will continue during Phase VI as well.

L2s and Multichain Strategies

A core priority for Phase VI will be the continued development of GHO’s multichain strategy, centered around the use of one facilitator on mainnet, the use of the CCIP bridge, and the implementation of GSMs on destination chains. These Stability Modules will be pre-filled by the mainnet facilitator, enabling native swaps into GHO on arrival chains and eliminating the need for inefficient bridging.

This architecture significantly enhances capital efficiency by allowing users to mint or swap GHO directly on their preferred chain. It also addresses one of the key friction points observed in Phase V, as bridging has proven to be a major brake on growth. By enabling native, trust-minimized GHO access across chains, the stataGSMs will remove barriers to adoption and improve user experience across ecosystems.

The modified stataGSM is currently in the last stages of review with @TokenLogic and @AaveLabs.

Sonic, Avalanche and Gnosis

Three key chains are being targeted for GHO deployment in the near future: Sonic, Avalanche, and Gnosis. Each of these networks offers a unique opportunity to tailor GHO’s integration to the strengths of the local ecosystem.

On Sonic with @TokenLogic leading the deployment, the ALC plans to position GHO at the heart of one of the most innovative DeFi environments currently emerging. The goal is to create strong synergies with leading protocols such as Pendle, Rings, Beets, and Silo. Sonic offers a highly composable, fast-moving landscape where GHO can fit perfectly.

On Avalanche, with @AaveLabs leading the deployment, GHO will benefit from the support of the Avalanche Foundation, which is preparing to launch new incentive programs at the chain level. The ALC is working to ensure that GHO is a key participant in these initiatives. The playbook established with Balancer v3 on Ethereum may be replicated here, with additional attention to exploring synergies with Avalanche’s native stablecoin AUSD. This deployment will be focused on ecosystem-wide coordination.

On Gnosis, the vision is centered on integrating GHO into the Gnosis Card ecosystem. The objective is to streamline both on- and off-ramping processes. The ALC will work closely with KPK and the Gnosis Foundation to facilitate this integration, creating a seamless user experience for payments, transfers, and financial access via GHO on Gnosis.

Performance Metrics

The below details some high-level GHO metrics:

DescriptionEthereumArbitrumAvalancheBase
TVL DEX Liquidity Pools85M10M10M20M
TVL Utility Liquidity Pools (Excl. stkGHO)15M5M5M5M
DEX Liquidity Composition< 50% GHO (< 33% for 3pools)< 50% GHO (< 33% for 3pools)< 50% GHO (< 33% for 3pools)< 50% GHO (< 33% for 3pools)
Swap Price Impact $5M Swap (GHO to USDC)< 0.10%< 0.25%< 0.25%< 0.25%
Annualised Peg Volatility< 5.00%< 5.00%< 5.00%< 5.00%
Price level for >90% time$0.995$0.995$0.995$0.995

Please note, each of the above targets has external dependencies beyond the control of the ALC. The above table serves as a North Star for the ALC to strive towards over the next three months. Having measurable targets provides a clear direction and goal to achieve.

Specification

Create allowance for the ALC to withdraw 3,500,000 aEthLidoGHO from the Ethereum collector. 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's specification is a single, fairly narrow claim: grant the ALC SAFE an allowance to withdraw 3,500,000 aEthLidoGHO from the Ethereum Collector. The only decoded on-chain action is a generic execute() call to a payload contract address, which is the typical Aave governance delegatecall pattern — the actual logic (approve() call, amount, recipient) lives inside that payload contract's bytecode/source and is not surfaced in the decoded calldata provided here. Because the decoded action carries no arguments (amount, token, recipient), there is no way to directly cross-check the $3.5M figure or the SAFE address against the calldata itself. I did not find any contradiction between the description and the one visible action — the execute() call is consistent with what a governance proposal implementing this specification would look like — but I also cannot positively confirm the specific numeric/address details claimed in the prose from the calldata alone. This is a structural limitation of the decoding depth rather than an actual mismatch, so I am not flagging a discrepancy, but confidence is marked low because the comparison is not fully verifiable at this level of decoding.

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
0x183f…a604
Value
0 wei
Function
fallback()
Arguments
{}
Calldata

05Tally

Summed from votes

Voters51
VP participating560.3K
Outcome (current)For
Current support100%

06Voters

51 total
Filter:
VoterChoice% of totalRationale
570x57ab…2922For279.2K49.83%—2y ago
2E0x2e21…f21aFor124.3K22.19%—2y ago
B90xb933…8dd1For39.6K7.07%—2y ago
3D0x3ddc…05b0For30.1K5.36%—2y ago
870x8787…ea52For24.7K4.41%—2y ago
EC0xecc2…6ac9For21.1K3.76%—2y ago
EZezr3al.eth0x8659…7d0eFor12.4K2.21%—2y ago
8B0x8b37…2a22For10.9K1.95%—2y ago
070x0703…961bFor10K1.78%—2y ago
2C0x2cc1…4df1For4.6K0.82%—2y ago
080x0865…24ceFor2K0.36%—2y ago
AD0xad21…f892For8010.14%—2y ago
B30xb356…c826For480.30.09%—2y ago
0B0x0ba4…2b9dFor99.90.02%—2y ago
640x649f…35b8For10.20.00%—2y ago
FE0xfefc…79fbFor8.20.00%—2y ago
D00xd059…0028For5.50.00%—2y ago
C30xc348…898eFor3.50.00%—2y ago
050x0579…4048For3.10.00%—2y ago
2F0x2f2f…f78aFor20.00%—2y ago
010x019e…2ee3For0.30.00%—2y ago
160x168f…7400For0.10.00%—2y ago
7F0x7f21…31e0For00.00%—2y ago
EE0xee2a…58a7For00.00%—2y ago
D70xd712…1366For00.00%—2y ago
A00xa0d0…604aFor00.00%—2y ago
930x93e0…f6eeFor00.00%—2y ago
950x95d2…88f9For00.00%—2y ago
4D0x4d12…7d7cFor00.00%—2y ago
BE0xbef8…9999For00.00%—2y ago
140x1475…6e15For00.00%—2y ago
E60xe6b8…452dFor00.00%—2y ago
210x21ff…c5a8For00.00%—2y ago
380x38dc…472dFor00.00%—2y ago
D20xd248…32aeFor00.00%—2y ago
150x1523…080fFor00.00%—2y ago
A60xa6ac…2bf3For00.00%—2y ago
AC0xacc9…0b28For00.00%—2y ago
C40xc4cd…47bcFor00.00%—2y ago
7A0x7a04…17a8For00.00%—2y ago
360x36ba…b435For00.00%—2y ago
E20xe274…1542For00.00%—2y ago
700x704b…7a63For00.00%—2y ago
E80xe8ee…0877For00.00%—2y ago
ED0xed4c…9508For00.00%—2y ago
E50xe5bd…7091For00.00%—2y ago
2A0x2a90…78a2For00.00%—2y ago
220x22ff…cc99For00.00%—2y ago
9E0x9e41…3054For00.00%—2y ago
490x49a4…9023For00.00%—2y ago
Showing 50

07Forum

No forum thread is confidently linked to this proposal.