• © Goverland Inc. 2026
  • v1.0.8
  • Privacy Policy
  • Terms of Use
Event HorizonEvent Horizonby0xFAD69Bd739c64cC8e3f1C3bb3B60fe4f160174Cchvax.eth

[AAVE] Deploy 10M GHO into Aave v3 Lido Instance

Voting ended about 1 year agoSucceeded

Simple Summary

Following the addition of GHO to the Lido instance of Aave v3 on Ethereum, this publication proposes supporting GHO liquidity by minting 10M units of GHO and depositing into Aave Lido.

Motivation

By providing liquidity on the Lido instance, the Aave DAO shall provide the initial bootstrapping liquidity in a very cost efficient manner and, in doing so, enhance the DAO's revenue generated from the Lido instance. GHO holders will be able to deposit GHO to earn the deposit yield whilst benefit from small than otherwise concentration risk within the reserve due to the DAO providing the bootstrapping liquidity.

With strong demand for GHO using wstETH as collateral resulting in 23.7% of GHO supply sourced from the Main market being backed by wstETH, this demonstrates that users actively seek to benefit from the capital efficiency of using an LST as collateral. Deploying additional GHO into the Lido instance is expected to further encourage this positive behavior, reinforcing the appeal of wstETH as a reliable, yield-bearing collateral for GHO.

Specification

  • Prior to proposal, GhoDirectMinter contract was deployed here
  • Grant RISK_ADMIN_ROLE to GhoDirectMinter referenced above
  • Add GhoDirectMinter as a GHO token facilitator
  • Mint 10M GHO and supply into Aave Lido
  • Allow GhoBucketSteward to control GhoDirectMinter

References

  • Implementation: AaveV3EthereumLido
  • Tests: AaveV3EthereumLido
  • Snapshot
  • Discussion

Copyright

Copyright and related rights waived via CC0.

https://app.aave.com/governance/v3/proposal/?proposalId=227

Off-Chain Vote

YAE
47 HVAXVC100%
NAY
0 HVAXVC0%
Quorum:4700%
Download mobile app to vote

Discussion

Event Horizon[AAVE] Deploy 10M GHO into Aave v3 Lido Instance

Timeline

Jan 07, 2025Proposal created
Jan 08, 2025Proposal vote started
Jan 10, 2025Proposal vote ended
Mar 26, 2026Proposal updated