[Proposal] Authorize Gauntlet for Oracle Pools

This proposal also appears on Balancer's forum.

Three weeks ago, Balancer governors voted to allow Gauntlet to set swap fees on pools deployed from the WeightedPoolFactory. At the time, this was the only Balancer V2 pool factory available; but since then, another specialization has been deployed for two-token pools which provide TWAP oracles. This proposal seeks to grant the same authorization to Gauntlet, but for the new pool factory.

Motivation

Please consult the original proposal for the full details. In short, this authorization would apply only to pools using the delegated owner address (0xBA1BA1ba1BA1bA1bA1Ba1BA1ba1BA1bA1ba1ba1B). For those pools which have opted in, Gauntlet's power would extend only to the swap fee; Gauntlet cannot alter any other attributes of the pool nor extract funds.

Specification

The Balancer Governance Multisig would submit one transaction as follows. Here, "Multisig" refers to the Gnosis Safe at 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f and "Authorizer" is the smart contract at 0xA331D84eC860Bf466b4CdCcFb4aC09a1B43F3aE6.

1. Grant Gauntlet the ability to set swap fees on pools deployed from the WeightedPool2TokensFactory Multisig -> Authorizer -> grantRole(0xc065d550fa98abc242b6baf98e7b2063590675f1ddd81bdb9ea8d8f5c5d52f98, 0xE4a8ed6c1D8d048bD29A00946BFcf2DB10E7923B);

For transparency's sake, a developer could reproduce the bytes specifying the role above using this pseudo-code:

pool.getActionId(pool.interface.getSighash('setSwapFeePercentage')); // 0xc065d550fa98abc242b6baf98e7b2063590675f1ddd81bdb9ea8d8f5c5d52f98