[BIP-28] Kill CREAM/WETH Gauge

Motivation

Since the approval of the CREAM/WETH gauge back on May 24th Balancer has earned ~$12k in protocol fees while spending ~$1.55M worth of BAL emissions. The CREAM gauge is the largest recipient of BAL emissions while returning virtually zero fee revenue to the protocol. Long term mechanisms like the recently passed “core pools” proposal should help naturally correct this imbalance as market forces are given time to work though even in an optimistic scenario the CREAM gauge will remain very large for the foreseeable future.

Per recent discussion on the forum the community is split on this issue. Governance did approve the CREAM gauge in a legitimate vote and BAL was bought on the open market and locked in veBAL to vote for it. Governance also has the power to vote to kill any gauge for any reason and everyone participating in veBAL accepts these are the rules.

The Balancer ecosystem has significant funding requirements that currently far exceed our revenue generation based on the last 30 days. At this point in time the largest blocker to Balancer reaching sustainability is the existence of the CREAM gauge. There is enough support in the community for killing the gauge that it is appropriate to move this to a vote in my view - this proposal will be sent to the Governance Council for approval next Thursday, July 14th.

Specification

If approved, the DAO Multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will call grantRole on the Authorizer 0xA331D84eC860Bf466b4CdCcFb4aC09a1B43F3aE6 with the following arguments:

role: 0xec1d467d9ab03a0079c22a89037209f5763aec973897ea763e2cf25d71a5f12e account: 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f

The role can be verified here. This will give the DAO Multisig the ability to call killGauge on a pool's gauge.

The DAO Multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will then call killGauge on the CREAM/WETH Gauge 0x9F65d476DD77E24445A48b4FeCdeA81afAA63480