[BIP-489] Kill Xave FXPool Gauges

PR with Payload


Recently the Xave Finance team recently was notified of a potential bug report. As advised by the team, removing all liquidity is best for LPs at this time. The Xave team has communicated to the Maxis that their plan is to deploy new pools and disclose further information on the situation in the near future. Due to this migration, there is no sense in incentivizing liquidity via Balancer gauges, and killing all currently active ones is the best way forward.

Network Symbol Root Gauge PoolId
Ethereum BPT 0xe629c43bcad1029e12ed51432b9dd3432b656cc9 0xad0e5e0778cac28f1ff459602b31351871b5754a0002000000000000000003ce
Ethereum L-GPT-USDC 0xc5e66bB9fE27b7Cef4B64557Ad8398437730DD33 0xc58150838855a5605c9030398c6d22afd5bb09ee00020000000000000000061b
Polygon BPT 0x145011e0c04805e11bef23c1eed848faf49bb779 0x726e324c29a1e49309672b244bdc4ff62a270407000200000000000000000702
Avalanche BPT 0x40b4c2e260f803f868053789bd4a6c7edd1cdc39 0x55bec22f8f6c69137ceaf284d9b441db1b9bfedc000200000000000000000011


The DAO Multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will interact with the AuthorizerAdaptorEntrypoint at 0xf5dECDB1f3d1ee384908Fbe16D2F0348AE43a9eA and call performAction using 0xab8f0945 for the data(bytes) argument and use each ‘Root Gauge’ address as the target(address)

1 Like