[BIP-888] Migrate mainnet rETH Gauge

PR with Payload

Summary:

This proposal outlines a plan to immediately migrate the mainnet rETH pool from the now-deprecated v2 rETH/WETH pool to the newly-created v3 rETH-waEthWETH pool.

This would be done by killing the gauge of the now-deprecated pool (already completed), and adding the new gauge of the newly-created pool to the controller as soon as possible.

Any remaining pool recycled fees generated by the now-deprecated pool will be directed to the new pool gauge effective upon the new gauge being added to the controller.

Motivation:

This migration needs to happen rapidly, due to the sudden closing of the v2 pool due to a security issue. The new pool uses a v3 contract, which addresses that concern. Independently, the Rocket Pool incentives management committee had decided to move to a pool paired against Aave-ETH instead of WETH for greater efficiency.

Technical Specification:

Gauge Adds:

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

gauge(address): 0x62a66eb9abf7a788f48d0ce7c0c065df9e09da19

gaugeType(string): Ethereum

Configuration:

alliance_fee_share.json will have the first pool in the “Rocket Pool” entry changed:

    {
      "name": "Rocket Pool",
…
      "pools": [
        {
          "pool_id": "0x1ea5870f7C037930CE1d5d8d9317c670e89e13E3",
          "network": "mainnet",
          "partner": "Rocket Pool",
          "eligibility_date": "2025-04-15",
          "active": true
        },
…
      ]
    },
1 Like

Edit by MAXYZ:

  • assign BIP ID
  • add payload

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