[BIP-156] Authorize Migration to GaugeAdder v3

Governance General Proposal
1

Motivation

As part of the coming migration to the Timelock Authorizer described in BIP-140 the Gauge Adder v2 also must undergo a migration to be compatible with the new authorizer.

The only differences from the old one is

  • that it supports the new authorizer that we’re migrating to (old one will break after migration)
  • it allows multiple gauges per pool on ethereum mainnet now.

Specification

If approved, the DAO Multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will initiate a transaction to interact with the Authorizer 0xA331D84eC860Bf466b4CdCcFb4aC09a1B43F3aE6 calling grantRole with the following arguments:

role: 0x0000000000000000000000000000000000000000000000000000000000000000

address: 0xE0f34c6AD719e6877062B7D97E12c61c096509AF

This can be verified here.

Additionally, the code for this migration can be viewed here.

In order to execute the migration, the DAO Multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will initiate a transaction to interact with the GaugeAdderMigrationCoordinator 0xE0f34c6AD719e6877062B7D97E12c61c096509AF calling performNextStage()

2

Note that if this passes the example will need to be updated with the new addr address here:

3

yep good call out.

new address will be here balancer-v2-monorepo/mainnet.json at master · balancer-labs/balancer-v2-monorepo · GitHub

will be in force once the timelock authorizer is turned on

4

Proposed Multisig Payload:

5

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