Motivation
With the Aave v3 linear pool wrappers being deployed this week and in the near future the ecosystem is migrating to various Boosted Aave v3 pools. To add to the migration process, i propose the qETH/WETH gauge to be killed, and a new qETH/bb-a-WETH gauge to be activated. This follows the same timeline as the previous migration proposed here, giving LPs enough time to migrate their positions and new pools to bootstrap themselves in the BIP-19 cycles. See qETH’s original proposal for relevant information to their token.
We will be coordinating with the various bribe marketplaces to ensure all future voting incentives only go towards the new gauges. The old pool will no longer have core pool status, the new pool / gauge will be a “core pools” under BIP-19. The 2% gauge cap will be maintained in the new gauge.
Pool being migrated:
Original deployment → New pool address
qETH / WETH → qETH / bb-a-WETH (Ethereum)
Adding qETH/bb-a-WETH Gauge (Ethereum)
Pool: 0x04248AAbca09E9a1a3D5129a7ba05b7F17DE7684
Gauge: 0xC764B55852F8849Ae69923e45ce077A576bF9a8d
Transaction:
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 qETH / bb-a-WETH gauge and be executed immediately. Part B will kill the gauge outlined above and be executed on May 9th.
Part A:
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 0xC764B55852F8849Ae69923e45ce077A576bF9a8d and the corresponding gauge type for the data(bytes) argument.
data(bytes) : 0x3a04f900000000000000000000000000c764b55852f8849ae69923e45ce077a576bf9a8d0000000000000000000000000000000000000000000000000000000000000002
Killing Old Gauge
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.
qETH / WETH → 0xE7ec5216ff485abffd9d390B82A5D742155f3A6f
data(bytes):
0xab8f0945000000000000000000000000E7ec5216ff485abffd9d390B82A5D742155f3A6f0000000000000000000000000000000000000000000000000000000000000002