PR with Payload
Motivation
I propose killing the following gauges (and the reasons for each action):
wstETH/weth (mainnet): This metastable pool has existed for a very long time. Unfortunately the parameters are immutable and with an amp factor of 50 the liquidity is simply not competitive in today’s landscape. Keeping this on the voting list creates confusion because it appears the same as the new wstETH/weth composable stable pool which has an amp factor of 5000 and will generate significantly more volume & protocol revenue. All emissions should be directed on this new pool.
wstETH/weth (Arbitrum): exact same reason as the above.
List of root gauges:
wstETH/weth (mainnet) → 0xcD4722B7c24C29e0413BDCd9e51404B4539D14aE
wstETH/weth (Arbitrum) → 0xDf464348c4EC2Bf0e5D6926b9f707c8e02301adf
Specification
The DAO Multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will interact with the AuthorizerAdaptorEntrypoint at 0xf5dECDB1f3d1ee384908Fbe16D2F0348AE43a9eA and call performAction using 0xab8f0945 for the data(bytes) argument and the root gauges listed for each pool above will be used for the target(address) argument.