Motivation
Through a continued analysis of our approved gauges I have identified five gauges that I believe should be migrated to a 2% cap. The historical and current activity (bribing/voting) has never approached the 2% limit and it is unlikely any of these would scale if they happen to be directed a large amount of BAL emissions. The relevant teams have been made aware of our plans and are in agreement on this course of action.
Gauges to be migrated: COW/WETH, COW/GNO, VITA/WETH (50/50), TEL/BAL/USDC, TEL/BAL
Specification
#1
If approved, 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 each one of the gauge addresses listed below and their corresponding gauge types for the data(bytes) argument. Each gauge will be its own transaction, thus there will be a total of 5 transactions.
List of contracts
0x7C777eEA1dC264e71E567Fcc9B6DdaA9064Eff51
0x57AB3b673878C3fEaB7f8FF434C40Ab004408c4c
0x777C45BD0a2AF1dA5fe4a532AD6B207D3CEd8b2d
0x7C56371077fa0dD8327E5C53Ee26a37D14b671ad
0xe0779Dc81B5DF4D421044f7f7227f7e2F5b0F0cC
#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.
The new capped gauges will be live for voting by September 15th. The old gauges will be killed on September 21st. This allows enough time for votes and bribes to be moved over to the new capped gauges.
On September 21st, the DAO Multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will interact with the AuthorizerAdaptor at 0x8F42aDBbA1B16EaAE3BB5754915E0D06059aDd75 and call performAction using 0xab8f0945 for the data(bytes) argument and the following list of contracts for the target(address) argument. Each contract will be its own transaction, thus there will be a total of 5 transactions.
List of gauge contracts
COW/GNO → 0xA6468eca7633246Dcb24E5599681767D27d1F978
COW/WETH → 0x158772F59Fe0d3b75805fC11139b46CBc89F70e5
VITA/WETH 50/50 → 0x055d483D00b0FFe0c1123c96363889Fb03fa13a4
TEL/BAL/USDC → 0x397649FF00de6d90578144103768aaA929EF683d
BAL/TEL → 0xC6FB8C72d3BD24fC4891C51c2cb3a13F49c11335