[BIP-686] Enable Gauge for 60GOLD/40st-yETH Pool

PR With Payload:

Golden Milestones

After many successful adventures on both Base and Arbitrum, the GoldenBoys have reached some important milestones. With that, it is now time to deploy the next step in the Golden Master Plan, which is to expand to the safest blockchain in existence: the Ethereum network!

The Gates are Open

$GOLD has already been successfully deployed on Ethereum for a while: https://etherscan.io/token/0x9deb0fc809955b79c85e82918e8586d3b7d2695a. The Stargates have also been aligned, allowing seamless bridging of $GOLD between its three chains.

All that is left now is for the Golden Gauges to also migrate. A lot of different options have been discussed, and to make the process easier I am proposing to kill all of our current gauges:

  • 5% 50GOLD/25WETH/25USDC on Base (0xdAe8AC766eB1c4Bb76Bc814FdE22AC46F467C51b)
  • 2% 33GOLD/33BAL/33USDC on Base (0x7B3EF4cAD077d871499285A2A8a1Cee0Ee122137)
  • 6% 50GOLD/25USDC/25wstETH on Arbitrum (0xcF853F14EF6111435Cb39c0C43C66366cc6300F1)
  • 2% 25GOLD/25BAL/25AURA/25wstETH on Arbitrum (0x159be31493C26F8F924b3A2a7F428C2f41247e83)

In return for a 10% capped gauge on the 60GOLD/40St-yETH pool on Ethereum (https://balancer.fi/pools/ethereum/v2/0xcf8dfdb73e7434b05903b5599fb96174555f43530002000000000000000006c3). Killing is to take place at least one epoch after the new gauge has been enabled.

Link to Gauge: Vyper_contract | Address 0xC219821b1FE1bBe436f62D911F00Ef1C8542A8F7 | Etherscan

Triforce

That is right! We are pairing up with the yield bearing st-yETH by Yearn. Note that this pool is configured with a reviewed rate provider, adding additional value for Balancer.

This move, together with the upcoming launch of Balancer V3, will enable the Boys to cook up some absolutely unimaginable DeFi tech!

Let’s build a Golden Triforce where everybody wins!

Technical Specifications:

Transaction: The Balancer Maxi LM Multisig eth:0xc38c5f97B34E175FFd35407fc91a937300E33860 will interact with the GaugeAdderv4 at 0x5DbAd78818D4c8958EfF2d5b95b28385A22113Cd and call the addGauge function with the following arguments:

gauge(address): 0xC219821b1FE1bBe436f62D911F00Ef1C8542A8F7

gaugeType(string): Ethereum

One week after approval of this gauge, at earliest week 37 2024, the DAO Multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will interact with the AuthorizerAdaptorEntrypoint at 0xf5dECDB1f3d1ee384908Fbe16D2F0348AE43a9eA and call performAction using 0xab8f0945 for the data(bytes) argument and “Root Gauge Address” from the list below as the target argument for each pool:

Network Pool Symbol Root Gauge
Base 50GOLD/25WETH/25USDC 0xed0bb13496ce24efff8f9734a9707d092d4be10c
Base GOLD/BAL/USDC 0xbf8f01ebcf0a21c46d23ada2c86eb31c9965b2f0
Arbitrum 50GOLD-25USDC-25WSTETH 0xa8d4b31225bd6faf1363db5a0ab6c016894985d1
Arbitrum GOLD-BAL-AURA-wstETH 0x86cf58bd7a64f2304227d1a490660d2954db4a91
3 Likes

This seems like a very nice compromise for the ecosystem and Goldenboys to both win here. Question for me is did you make a gauge for this pool yet? If not I am happy to do so; and prepare a payload once the post has some more feedback.

Agreed with @ZenDragon

This is a nice compromise of shifting focus to this new pool while having a healthy balance in gauge weight allocation.
Full support.

Not yet, please do so. Thanks!

https://snapshot.org/#/balancer.eth/proposal/0x443e2c7fd9d85df70cad4bd2f7c4aa4d8fd16d04940ed81df40a198666af7128