PR with Payload
[BIP-413]: Kill GHO Gauges Week 35
Date: 28/08/2023
Author: @TokenLogic
Summary
The purpose of this publication is to kill three GHO gauges:
- GHO/DAI/USDC/USDT
- GHO/OHM
- GHO/MAI
These gauges either reduce the value proposition of other gauges that have less integration potential within the Aave ecosystem or have failed to attract any deposit liquidity since being initially deployed.
Motivation
The GHO/USDC/USDT Gauge has the potential to create a new 3pool that which has the potential to be included in the Aave Safety Module (SM). It is sub optimal for incentives to be split between the current GHO/3pool and pending GHO/USDC/USDT Gauge.
The OHM and MAI Gauges have been deployed since GHO launched on Balancer and have received no support. This is the results of various initiatives not coming to fruition.
Specification
The DAO Multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will interact with the AuthorizerAdaptorEntrypoint at 0xf5dECDB1f3d1ee384908Fbe16D2F0348AE43a9eA and call performAction using 0xab8f0945 for the data(bytes) argument and the “Gauge Address” list for each pool below will be used for the target(address) argument.
Gauge Addresses:
GHO/DAI/USDC/USDT - 0x414eae9a827f4174a63fe4f10e975678ca28c898
GHO/OHM - 0x73f49a29f91e016cc9bde5cdf6f5dc049280e5a9
GHO/MAI - 0x5c23661e747f84e0c71d782e5f1513126041734b
Disclosure
TokenLogic receives no payment from Aave DAO or any external source for the creation of this proposal. TokenLogic is a delegate within the Aave ecosystem.