CEX Earn Funding Proposal
01Summary
Aave DAO proposes allocating 5M GHO from treasury over 4-6 months to fund a CEX Earn program that will distribute weekly GHO rewards to users holding GHO on centralized exchanges like Bybit and Bitget, plus market maker liquidity and marketing support to drive GHO adoption and compete with established stablecoins.
- Type
- treasury allocation
- Funding
- $5M GHO (approximately $5M at GHO parity with stablecoins)
Key changes
- Allocate 5M GHO from DAO treasury to CEX Earn incentive program over 4-6 months(high)
- Swap 2.5M USDT and 2.5M USDC for GHO to fund the program(high)
- Implement weekly GHO airdrop rewards to users holding GHO on participating CEXs with variable yield rates (adjusted weekly, with TVL cap to limit spending)(high)
- Fund market maker engagement and technical integration costs with CEXs for GHO listings(medium)
- Fund marketing support to promote GHO onboarding and CEX listings(medium)
Notable concerns
- Program yield will exceed Aave Protocol deposit rates, creating potential budget exposure that will be managed through weekly yield adjustments and TVL caps
- Revenue from GSM activities will accumulate separately from rewards distributed, creating timing and yield differences that need coordination
- Success depends on GHO's differentiation from entrenched stablecoins like USDT and USDC already on CEXs
- Program is temporary (4-6 months) and requires sustained adoption to retain users after rewards are reduced
Generated by Kvorum
02Description
Simple Summary
To maximize the impact of GHO’s upcoming listings on Bybit, Bitget, and other centralized exchanges (CEXs), this publication proposes engaging a market maker to provide spot liquidity and allocating funds to a CEX Earn program to drive broader adoption of GHO.
Motivation
Listing GHO on centralized exchanges serves as a strategic lever to broaden its adoption by tapping into a wider and more diverse user base. It opens a powerful new distribution channel, allowing the Aave DAO to strengthen GHO’s market presence and accelerate its global reach.
- Expanded Audience: Access to retail and institutional users who primarily operate on CEXs and are less familiar with decentralized and on-chain stablecoins.
- New Utility: Enables GHO to be used as collateral in perpetual contracts and other financial products not currently available within DeFi.
- Enhanced Liquidity and Visibility: CEX listings improve global accessibility and strengthen GHO’s brand recognition through higher trading volumes and broader market exposure.
While several stablecoins are already entrenched on centralized platforms, GHO’s success will hinge on delivering a compelling value proposition that differentiates it from more established alternatives. By leveraging the Aave Protocol as a native yield engine, GHO can replicate the successful strategies of stablecoins like USDtb and USDe, channeling yield from the GSMs directly to CEX users, incentivizing them to hold and use GHO.
Earn Campaign Structure
To accelerate GHO’s adoption, we propose a user acquisition incentive that rewards users for simply holding GHO on the CEX—regardless of how or where it’s used on the platform. This mechanism mirrors the experience of depositing into an on-chain Earn vault, allowing users to earn yield passively while maintaining full flexibility.
By offering native yield on CEX-held GHO, we aim to drive broader usage across the exchange’s ecosystem—spanning spot, derivatives, and Earn products—while positioning GHO as a competitive and attractive alternative to existing stablecoins.
The GHO Earn Campaign offers the following features:
- sGHO-style Airdrop Model: A proxy system that tracks GHO balances on participating CEXs and rewards users on a weekly basis, mimicking the on-chain sGHO model.
- Incentives Distribution: Rewards will be distributed based on GHO balances held in eligible accounts on partner exchanges. Users will receive a weekly airdrop direct to their balance to create a savings account user experience.
This model encourages sustained holding of GHO while aligning with familiar incentive mechanisms used in CEX environments.
By offering a competitive yield that accelerates GHO’s broad adoption, we are able to advocate for further integrations beyond spot trading and Earn Platforms. Through offering greater utility such as Margin trading and Perpertuals, we expect to achieve higher retention rates when rewards are reduced.
Funding
The Earn program’s yield is expected to exceed the Aave Protocol deposit rate and be competitive compared to other offerings in the market.
In administering the program, GHO holders will received GHO airdrop to them each week. Users receive a fixed yield that is adjusted on a weekly cadence to be loosely correlated with the broader market. ie: Week 1 could be 6% and Week 2 could be 6.25%. However, to limit budget exposure there is a TVL target, once which once exceeded the yield is diluted to avoid over-spending.
While Aave generates revenue from the GSMs and in parallel distributes GHO to CEX users, there are both timing considerations and differences in yields to consider. By creating a separate budget, this streamlines the operational burden for sustaining the program. Revenue generated by the GSMs will accumulate independent of the rewards being distributed.
The true cost of the program is the difference between revenue generated from the new GHO circulating supply and the rewards distributed to bootstrap GHO across the CEXs. TokenLogic will provide a dashboard to track overall spend and revenue generated from activities linked to this program.
To execute this initiative, we are requesting a funding allocation of 5M GHO from the DAO treasury to be used for:
- Weekly rewards distribution (denominated in GHO or an equivalent stable asset).
- Technical integration and CEX collaboration costs.
- Marketing support to promote GHO onboarding and listings.
Proposed budget: 5M GHO over a 4 to 6 month period.
Specification
The initial Allowance is for 5M aEthLidoGHO from the Prime instance.
Asset: aEthLidoGHO 0x18eFE565A5373f430e2F809b97De30335B3ad96A
Amount: 5M
Spender: AFC 0x22740deBa78d5a0c24C58C740e3715ec29de1bFa
Method: approve() aEthLidoGHO on the Aave Collector contract to the AFC address.
To facilitate the program, the following assets are to be swapped for GHO.
| Ethereum | Amount | Swap |
|---|---|---|
| USDT | 2.50M | GHO |
| USDC | 2.50M | GHO |
References
- Implementation: AaveV3EthereumLido
- Tests: AaveV3EthereumLido
- Snapshot
- Discussion
Copyright
Copyright and related rights waived via CC0.
03Mismatch analysis
The decoded on-chain data consists of a single opaque call to a payload contract's execute()/fallback function, which is the standard Aave governance execution pattern: the DAO's governor calls a single payload contract that internally performs the granular actions (token approvals, swaps, etc.) described in the proposal text and linked Solidity implementation. Because the internal logic of the payload contract is not expanded in the provided decoded rows, I cannot line-item verify the exact approve() call to the AFC address or the USDT/USDC swap amounts against calldata directly. However, this single-action structure is routine and expected for Aave V3 proposals of this type, and the proposal provides a direct link to the implementation contract matching this address pattern, which is the normal way these are verified by delegates. No contradictory values, targets, or omissions are visible in the data provided, and nothing in the description appears inconsistent with what a payload of this type would do. Given the lack of expanded internal calldata, full certainty is not possible, so confidence is medium rather than high, but there is no evidence of a mismatch, so the assessment is consistent rather than a discrepancy of any kind.
Generated by Kvorum
04Actions
- Target
- 0x5355…d0b3
- Value
- 0 wei
- Function
- fallback()
- Arguments
{}- Calldata
05Tally
Summed from votes
06Voters
| Voter | Choice | % of total | Rationale | ||
|---|---|---|---|---|---|
| 570x57ab…2922 | For | 286.9K | 0.00% | — | 1y ago |
| EZezr3al.eth0x8659…7d0e | For | 40.6K | 0.00% | — | 1y ago |
| B90xb933…8dd1 | For | 39.6K | 0.00% | — | 1y ago |
| EC0xecc2…6ac9 | For | 25K | 0.00% | — | 1y ago |
| 870x8787…ea52 | For | 24.8K | 0.00% | — | 1y ago |
| 3D0x3ddc…05b0 | For | 20.1K | 0.00% | — | 1y ago |
| 7A0x7ae1…e585 | For | 10K | 0.00% | — | 1y ago |
| 2C0x2cc1…4df1 | For | 5.2K | 0.00% | — | 1y ago |
| 080x0865…24ce | Against | 2K | 0.00% | — | 1y ago |
| 620x6276…b4e8 | For | 1.2K | 0.00% | — | 1y ago |
| 0E0x0e00…ccfc | For | 797.1 | 0.00% | — | 1y ago |
| 440x4444…34b3 | For | 744.1 | 0.00% | — | 1y ago |
| B30xb356…c826 | For | 480 | 0.00% | — | 1y ago |
| A50xa54f…0f31 | For | 459.8 | 0.00% | — | 1y ago |
| 7D0x7dbf…1ab5 | For | 147.3 | 0.00% | — | 1y ago |
| F10xf13c…6dd3 | For | 141.6 | 0.00% | — | 1y ago |
| B80xb8ab…cc8b | For | 22.9 | 0.00% | — | 1y ago |
| 920x92a7…efaf | For | 12.1 | 0.00% | — | 1y ago |
| 640x649f…35b8 | For | 10.4 | 0.00% | — | 1y ago |
| 7E0x7e6c…73eb | For | 4.9 | 0.00% | — | 1y ago |
| 2F0x2f2f…f78a | For | 2 | 0.00% | — | 1y ago |
| 050x0579…4048 | For | 1 | 0.00% | — | 1y ago |
| 010x019e…2ee3 | For | 0.3 | 0.00% | — | 1y ago |
| 6E0x6e54…aea3 | For | 0.3 | 0.00% | — | 1y ago |
| 010x0100…7cc9 | For | 0.2 | 0.00% | — | 1y ago |
| 040x0429…dab6 | For | 0.1 | 0.00% | — | 1y ago |
| 790x79fa…0275 | For | 0.1 | 0.00% | — | 1y ago |
| F40xf404…9b14 | For | 0 | 0.00% | — | 1y ago |
| E40xe408…738d | For | 0 | 0.00% | — | 1y ago |
07Forum
No forum thread is confidently linked to this proposal.
08Similar proposals
- aaveexecutedGHO Funding88%
- aaveexecutedAave Liquidity Commitee Funding86%
- aaveexecutedAave Liquidity Committee Funding Phase VI84%
- aaveexecutedFund GHO Liquidity Committee83%
- aaveexecutedOnboard GHO and Migrate Streams to Prime Instance83%
- aaveexecutedAave Liquidity Committee Funding Phase IV82%
- aaveexecutedGHO Mainnet Launch81%
- aaveexecutedDeploy 10M GHO into Aave v3 Lido Instance81%
- aaveexecutedGHO Gnosis Launch81%
- aaveexecutedsGho Launch81%