Balancer

PR with payload: https://github.com/BalancerMaxis/multisig-ops/pull/35

Motivation

As part of the ongoing process to transition to the timelock authorizer the Maxis have temporarily lost the ability to add gauges the traditional way. Once the migration to the new authorizer and to the Gauge Adder v3 is complete then that ability will be restored. We’re currently targeting the end of February for this to be done. Until then, any new gauge must be added by the DAO Multisig directly. BIP 159 & 160 were not written with the specification required to do this. After communicating with the teams involved they desire to proceed immediately with the adding of their gauges rather than waiting another month. This proposal will add their already approved gauges directly from the DAO Multisig.

It’s also important to note that once we trigger the next stage of the Gauge Adder v3 migration there will be a 14 day window where no new gauges can be added by any method. This is expected to begin on Feb 13th or so.

Specification

#1 The DAO Multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will initiate a transaction to the Authorizer 0xA331D84eC860Bf466b4CdCcFb4aC09a1B43F3aE6 calling grantRole with the following arguments:

role: 0xf49d7ffb5922642adc9f29cfb52b2214e81e0b0e54e9cd1e9f70439f0011f368

This corresponds with the role for calling add_gauge on the gaugeController as seen here .

account: 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f

This allows the DAO Multisig to directly add gauges to the controller.

#2

The DAO Multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will interact with the AuthorizerAdaptor at 0x8F42aDBbA1B16EaAE3BB5754915E0D06059aDd75 and call performAction with the GaugeController at 0xC128468b7Ce63eA702C1f104D55A2566b13D3ABD for the target(address) argument and using 0x3a04f900 followed by the gauge addresses below and the corresponding gauge type for the data(bytes) argument. There will be a total of 3 transactions.

gauges: EURS/USDC -> 0xE629c43BCad1029E12ED51432B9dd3432b656cc9 SD/USDC -> 0x4dC35eC8562596ddA6aEe8EceE59a76D4d72b83E SD/WETH -> 0x37eCa8DaaB052E722e3bf8ca861aa4e1C047143b

data(bytes) : EURS/USDC -> 0x3a04f900000000000000000000000000e629c43bcad1029e12ed51432b9dd3432b656cc90000000000000000000000000000000000000000000000000000000000000002 SD/USDC -> 0x3a04f9000000000000000000000000004dc35ec8562596dda6aee8ecee59a76d4d72b83e0000000000000000000000000000000000000000000000000000000000000002 SD/WETH -> 0x3a04f90000000000000000000000000037eca8daab052e722e3bf8ca861aa4e1c047143b0000000000000000000000000000000000000000000000000000000000000002

#3 The DAO Multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will initiate a transaction to the Authorizer 0xA331D84eC860Bf466b4CdCcFb4aC09a1B43F3aE6 calling renounceRole with the following arguments:

role: 0xf49d7ffb5922642adc9f29cfb52b2214e81e0b0e54e9cd1e9f70439f0011f368

This corresponds with the role for calling add_gauge on the gaugeController as seen here .

account: 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f

This removes the ability for the DAO Multisig to directly add gauges to the controller.