[BIP-763] Enable Boosted GHO 3pool on Balancer v3

PR with payload

Summary

In preparations for migrating GHO liquidity from Balancer v2 to v3, @TokenLogic proposes enabling the new Boosted 3pool gauge on Ethereum.

This pool is to be considered “core pool” under BIP-19, meaning the protocol fees earned by these pool would be used to bribe for votes on it.

Within this proposal legacy gauges not being used on Balancer v2 are to be sunset.

Motivation

With several GHO liquidity pools on Balancer v2, this publication begins the process by proposing to enable a new Boosted 3pool gauge and migrating liquidity from our largest liquidity pool across to Balancer v3.

The Boosted 3pool is to deploy each asset into Aave v3 to earn yield.

  • GHO into Aave Prime
  • USDC into Aave Core
  • USDT into Aave Core

For information specific to each of the constituents mentioned above, please refer to the following Balancer v2 forum post.

You can find detailed information about all these assets in the rate provider registry, which serves as a comprehensive source for all relevant details required for the review.

We will also, use this opportunity to sunset a few under-utilised gauges across Arbitrum and Ethereum.

The following Balancer v2 gauges are to be sunset:

Network Pool Gauge Address
Ethereum GHO/PYUSD #1 0xb71C90F165cf99d4004499fF058E265Aa68fAC85
Ethereum GHO/PYUSD #2 0xAf1b4bfA0a69B9e669d925888b99741E15e37253
Arbitrum GHO/USDC/USDT 0x7d907D8D66B6CAd285D4349F507EcdfD11FD23D2
Arbitrum USDe/waGHO 0xcfab2efef3affdd158568dc896115eac26b3c498

Specification

Enable Gauges

The Balancer Maxi LM Multisig 0xc38c5f97B34E175FFd35407fc91a937300E33860 will interact with the GaugeAdderv4 at 0x5DbAd78818D4c8958EfF2d5b95b28385A22113Cd and call the addGauge function with the following arguments based on the table above:

Pool address: 0x85B2b559bC2D21104C4DEFdd6EFcA8A20343361D
Gauge(address): 0x9fdD52eFEb601E4Bc78b89C6490505B8aC637E9f
GaugeType(string): Ethereum

Kill Gauges

The DAO Multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will interact with the AuthorizerAdaptorEntrypoint at 0xf5dECDB1f3d1ee384908Fbe16D2F0348AE43a9eA and call performAction using 0xab8f0945 for the data(bytes) argument and the “Root Gauge Address” list for each pool below will be used for the target(address) argument.

Disclosure

TokenLogic is a service provider to Aave DAO and receives no payment for creating this proposal.

1 Like

https://snapshot.org/#/s:balancer.eth/proposal/0xb4525d95c2696da4802905fee739ff1dfdd459962e63be01679d6ce1a65e9b84

1 Like