title: [TEMP CHECK] Allocating part of GHO Revenue to Safety Incentives
author: Marc Zeller, Aave-Chan Initiative (ACI)
This TEMP CHECK proposes the introduction of a dual reward system Safety Incentives, where a portion of GHO revenue is directed to the Aave Safety Incentives, enabling stakers (StkAAVE & StkBPT) to earn both AAVE and GHO tokens.
The motivation behind this TEMP CHECK is to enhance the sustainability of the Aave protocol by reducing its reliance on the Ecosystem Reserve of AAVE tokens for Safety Incentives. We propose a strategic shift towards harnessing protocol economic activity to generate “real yield” through the introduction of GHO as an additional Safety Incentive.
By directing part of GHO revenue to the Safety Incentives, we aim to create a dual reward system, offering stakers both AAVE and GHO tokens. While the contribution of GHO to Safety Incentives may initially be a small fraction of the total incentives, it represents a significant step towards the protocol’s maturity and sustainability.
This proposal, suggests that the governance should adjust the distribution percentage quarterly, in response to market conditions.
As the Aave protocol already generates sustainable revenue that covers service provider costs, the introduction of GHO into the Safety Incentives mix is a viable and strategic move toward diversifying Safety Incentives and ensuring the long-term sustainability of the protocol.
While technicals details of the implementation will be discussed at a potential ARFC stage of this proposal, and current stage is meant to gauge community’s general interest, here’s a diagram of a possible implementation, redirecting GHO revenue from Collector contract (dao treasury) to a splitter contract controlled by governance.
We propose to set a potential “Gho Splitter” contract with
- 80% toward COLLECTOR contract (Aave DAO treasury)
- 20% toward REWARDS_VAULT (controlling safety incentives)
- Wait for GHO deployment AIP vote result (a NAY outcome will make the current TEMP CHECK irrelevant)
- Gather feedback from the community.
- If consensus is reached on this TEMP CHECK, the proposal will be escalated to the TEMP CHECK Snapshot stage.
- If the TEMP CHECK Snapshot is successful, the proposal will be escalated to the ARFC stage for service provider feedback and implementation discussions.
The Aave Chan Initiative has not been compensated by any third party for publishing this TEMP CHECK.
Copyright and related rights waived via CC0.