Motivation
With the Aave v3 linear pool wrappers ready for deployment in the ecosystem various Boosted Aave v3 pools and pairings have started to crop up in the governance forum. In order to streamline the process of transitioning from the old Aave v2 pool and pairings I on behalf of the Maxis am proposing we close the loop by voting to kill the relevant gauges this week thereby permitting 3 more weeks of emissions on the pool gauges listed below. This will give LPs enough time to migrate their positions and new pools to bootstrap themselves in the BIP-19 cycles. As an adder, a new STG/bb-a-USD gauge will be activated with the execution of this proposal, along with the old one added to the kill list. The STG/bb-a-USD pool will be killed but the same information applies as in BIP-105.
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.
Pools being migrated:
Original deployment → New pool address
bb-a-USD → bb-a-USD (Ethereum)
STG / bb-a-USD → STG/bb-a-USD (Ethereum)
staBAL3 → 3pool (Ethereum)
MaticX / WMATIC → MaticX / bb-a-WMATIC (Polygon)
stMATIC / WMATIC → stMATIC / bb-a-WMATIC (Polygon)
Adding STG/bb-a-USD Gauge (Ethereum)
Pool: 0x639883476960a23b38579acfd7D71561A0f408Cf
Gauge: 0x454eb2f12242397688DbfdA241487e67ed80507a
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 bbaUSD/STG gauge and be executed immediately. Part B will kill the gauges outlined above and be executed on May 2nd.
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 0x454eb2f12242397688DbfdA241487e67ed80507a and the corresponding gauge type for the data(bytes) argument.
data(bytes) : 0x3a04f900000000000000000000000000454eb2f12242397688DbfdA241487e67ed80507a00000000000000000000000000000000000000000000000000000000000000002
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.
bb-a-USD → 0xa6325e799d266632D347e41265a69aF111b05403
data(bytes):
0xab8f0945000000000000000000000000a6325e799d266632D347e41265a69aF111b054030000000000000000000000000000000000000000000000000000000000000002
STG / bb-a-USD → 0x9703C0144e8b68280b97d9e30aC6f979Dd6A38d7
data(bytes):
0xab8f09450000000000000000000000009703C0144e8b68280b97d9e30aC6f979Dd6A38d70000000000000000000000000000000000000000000000000000000000000002
StaBAL3 → 0x34f33CDaED8ba0E1CEECE80e5f4a73bcf234cfac
data(bytes):
0xab8f094500000000000000000000000034f33CDaED8ba0E1CEECE80e5f4a73bcf234cfac0000000000000000000000000000000000000000000000000000000000000002
MaticX / WMATIC → 0x2C967D6611C60274db45E0BB34c64fb5F504eDE7
data(bytes):
0xab8f09450000000000000000000000002C967D6611C60274db45E0BB34c64fb5F504eDE70000000000000000000000000000000000000000000000000000000000000003
stMATIC / WMATIC → 0xf7C3B4e1EdcB00f0230BFe03D937e26A5e654fD4
data(bytes):
0xab8f0945000000000000000000000000f7C3B4e1EdcB00f0230BFe03D937e26A5e654fD40000000000000000000000000000000000000000000000000000000000000003