KVORUM
aaveSource: Aave governance v3 · #214

Onboard GHO and Migrate Streams to Prime Instance

executedDec 14, 2024, 04:33 PM UTCby570x57ab…2922

01Summary

AISummary by Kvorumclaude-haiku-4-5

Onboard GHO to Aave v3 Prime instance with 3M GHO seed from Collector, acquire 3M GHO from spot market, migrate Merit allowance from Core to Prime, and cancel AGD GHO allowance. GHO configured as borrow-only asset with 10.5% base variable borrow rate and included in sUSDe and ezETH eModes.

Type
protocol addition
Funding
$3,000,000

Key changes

  • Onboard GHO to Aave v3 Prime instance as borrow-only asset with 20M supply cap and 2.5M borrow cap(high)
  • Seed Prime instance with 3M GHO from Collector to sustain approximately two months of Merit program(high)
  • Acquire 3M GHO from spot market and send to Collector(high)
  • Configure GHO with 10.5% base variable borrow rate, 3% variable slope 1, and 50% variable slope 2(medium)
  • Add GHO to sUSDe eMode and ezETH eMode as borrowable asset(medium)
  • Migrate Merit allowance from Core to Prime market(medium)
  • Cancel Aave Grants DAO GHO allowance(medium)
  • Swap aUSDT (1.5M), aEthUSDT (0.5M), and aEthUSDC (1.0M) for GHO(medium)

Notable concerns

  • GHO configured as borrow-only asset without collateral eligibility may limit utility in certain market conditions
  • High borrow cap of 2.5M relative to 20M supply cap creates significant room for utilization imbalance
ContractsAave v3 Prime instanceGHO ReservesUSDe eModeezETH eMode
Generated by Kvorum
model: claude-haiku-4-5
provider: anthropic
profile: anthropic-fast-v1
prompt: v1.0
generated: 2mo ago
Read the description ↗

02Description

655 words

Simple Summary

This publication proposes the following:

  • Onboarding GHO to the Prime instance of Aave v3 with 3M seed from Collector;
  • Acquire 3M GHO from spot market and send to the Collector
  • Migrate Merit allowance
  • Cancel AGD GHO allowance

Motivation

Onboard GHO Prime Instance with 3M seed from Collector

With the circulating supply nearing 180M and nearly 50M in DEX liquidity on Ethereum, this publication proposes adding GHO to the Prime instance of Aave v3.

Adding GHO to the Prime instance of Aave v3 would provide the DAO with several opportunities:

  • Mint GHO through a Facilitator and deposit it into the Reserve to generate revenue;
  • Enable Aave DAO to earn yield on existing GHO holdings; and,
  • Establish a GHO reserve that provides an organic deposit yield.

Each of these options offers clear advantages for the Aave DAO and GHO users. GHO is to be onboarded as a borrow-only asset, similar to the current configurations of USDC and USDS.

The seeded 3M GHO should be sufficient to sustain two months of Merit, with a sufficient buffer to ensure timely fund withdrawals. Allowance will be migrated from Core to Prime market.

Acquire GHO from spot market and send to the collector

3M GHO is to be acquired from spot market and sent to the Collector.

Within this publication, the Aave Grants DAO GHO Allowance is to be cancelled.

Specification

The below details the parameter configuration of the GHO Reserve on the Prime instance of Aave v3.

ParameterValue
Isolation Modefalse
BorrowableENABLED
Collateral Enabledfalse
Supply Cap (GHO)20,000,000
Borrow Cap (GHO)2,500,000
Debt CeilingUSD 0
LTV0 %
LT0 %
Liquidation Bonus0 %
Liquidation Protocol Fee0 %
Reserve Factor10 %
Base Variable Borrow Rate10.50 %
Variable Slope 13.00 %
Variable Slope 250 %
Uoptimal92 %
FlashloanableENABLED
Siloed BorrowingDISABLED
Borrowable in IsolationDISABLED
Oracle0xD110cac5d8682A3b045D5524a9903E031d70FCCd

GHO is to be included in the sUSDe and ezETH eMode as shown below:

sUSDe eMode

ParameterValueValueValueValue
AssetsUSDeUSDSUSDCGHO
CollateralYesNoNoNo
BorrowableNoYesYesYes
Max LTV90%---
Liquidation Threshold92%---
Liquidation Bonus3.0%---

ezETH eMode

ParameterValueValueValueValue
AssetezETHUSDSUSDCGHO
CollateralYesNoNoNo
BorrowableNoYesYesYes
Max LTV75%---
Liquidation Threshold80%---
Liquidation Bonus7.5%---

This proposal includes swap the following asset for GHO:

Asset Holding
aUSDT (1.5M)
aEthUSDT (0.5M)
aEthUSDC (1.0M)

Cancel Aave Grants DAO GHO Allowance.

Migrate Merit allowance from Core to Prime market.

References

Copyright

Copyright and related rights waived via CC0.

03Mismatch analysis

AIMismatch analysis by Kvorumlow confidenceclaude-sonnet-5
Consistent

The proposal uses the standard Aave governance payload pattern: the decoded calldata consists of a single, argument-less execute() call to an external payload contract. This means the actual sub-actions (listing GHO on the Prime instance with specific risk parameters, seeding 3M GHO, migrating Merit allowance, cancelling the AGD allowance, swapping aTokens for GHO, and configuring eMode categories) are not individually visible in the decoded calldata — they are implemented inside the referenced Solidity payload contract (AaveV3EthereumLido_OnboardGHOAndMigrateStreamsToLidoInstance), which is linked in the References section and would need separate code review to verify parameter-level accuracy (caps, rates, oracle address, eMode LTVs, etc.). Because the on-chain calldata itself contains no verifiable parameters to compare against the detailed prose (rates, caps, LTVs, oracle address, swap amounts), I cannot confirm or deny value-level accuracy from calldata alone. There is no evidence of a mismatch — the single action target and signature are consistent with the expected governance execution flow for this type of multi-step DAO proposal — but the inability to inspect the payload's internal logic limits confidence. No red flags (e.g., unexpected recipient addresses, unrelated targets, or extra unexplained actions) are present in the decoded data, so I do not flag any discrepancy, but confidence in a full match is necessarily low given the opacity of the single delegatecall action.

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
0xf733…a8de
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.