Balancer

PR with payloads

https://github.com/BalancerMaxis/multisig-ops/pull/146 https://github.com/BalancerMaxis/multisig-ops/pull/147

Motivation

Aave v3 is recently available on Arbitrum and Polygon networks. This proposal contains four pools which are being migrated from their old gauges to new ones. The primary purpose of migrating the gauges is to utilize the Aave v3 market underneath, and also to move gauges from any pools in recovery mode to new implementations. These new gauges use the same cap percentage as the previous implementations and are compatible with the layer zero technology for cross chain boosts once the technology goes live, meaning no need to migrate these gauges in the near future. New pool gauges will be activated upon the vote passing, and gauges proposed to be killed will be executed 3 weeks from the passing of this proposal, in the case that it does.

We will be coordinating with the various bribe marketplaces to ensure all future voting incentives only go towards the new gauges. The old pools listed below will no longer have core pool status. All of the migrated pools will be restored as “core pools” under BIP-19. If a pool was not a core pool before this post, it will not become a core pool now.

Pools being migrated:

Original deployment → New pool address

wstETH/USDC → wstETH-BPT/bbaUSD (Arbitrum) BRZ/jBRL → BRZ/jBRL (Polygon) BRZ/jBRL / bbamUSD v2 → BRZ/jBRL / bbamUSD v3 (Polygon) frxETH / WETH → frxETH / bb-a-WETH (Polygon)

Transactions:

To allow time for emissions to move over and all LP’s to get the full benefit of AURA emissions this BIP will be executed in two parts. Part A will add the new gauges, and be executed immediately. Part B will kill the gauges outlined above and be executed on May 14th.

Part A - Adding New Gauges:

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 address (see list below) and the corresponding gauge type for the data(bytes) argument.

[wstETH-BPT/bbaUSD] → 0xd40a3C414Bb6f82fC5625e32895F49E53220f73b data(bytes): 0x3a04f900000000000000000000000000d40a3c414bb6f82fc5625e32895f49e53220f73b0000000000000000000000000000000000000000000000000000000000000004

[BRZ/jBRL] → 0x455f20c54b5712a84454468c7831f7c431aeEB1C data(bytes): 0x3a04f900000000000000000000000000455f20c54b5712a84454468c7831f7c431aeeb1c0000000000000000000000000000000000000000000000000000000000000003

[BRZ/jBRL / bbamUSD v3] → 0xBAdF0c8702B7Cb06bBEC351d18071804759e312c data(bytes): 0x3a04f900000000000000000000000000badf0c8702b7cb06bbec351d18071804759e312c0000000000000000000000000000000000000000000000000000000000000003

[frxETH / bb-a-WETH] → 0x416d15C36c6DaAd2b9410B79aE557e6F07DcB642 data(bytes): 0x3a04f900000000000000000000000000416d15c36c6daad2b9410b79ae557e6f07dcb6420000000000000000000000000000000000000000000000000000000000000003

Part B - Killing Old Gauges

Part B: 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 gauges for the target(address) argument.

[wstETH/USDC] → 0x87ae77A8270F223656D9dC40AD51aabfAB424b30

[BRZ/jBRL] → 0xF0d887c1f5996C91402EB69Ab525f028DD5d7578

[BRZ/jBRL / bbamUSD v3] → 0xE77239359CE4D445Fed27C17Da23B8024d35e456

[frxETH / WETH] → 0xEF3B68D9B6f44EeF2F6ea3d47D6e97707BF14189