[BIP-849] Kill Stale Gauges Q2 2025

PR With Payload https://github.com/BalancerMaxis/multisig-ops/pull/2138

Summary and Motivation

Per BIP-750 2025 Gauge Management the Balancer Maxis are responsible for killing gauges on a quarterly basis due to them becoming stale I.e. not voted for. The definition of stale as defined in the framework is a pool under 100k for >60 days and a pool without veBAL votes for >60 days. Removing these gauges from the system decreases overhead for gauge checkpointing, gas costs for the operation, and improves UX on the frontend and snapshot for gauge votes via Aura due to shorter lists and less clutter.

Updated Kill Criteria

• Per BIP-795 Kill Stale Gauges Q2 2025 gauge killing criteria was updated to flag a gauge as worth killing if it has not received veBAL votes for >60 days, and the median TVL has been under 100k USD equivalent for >60 days.
• The gauge killing list is now based on tracking by a defilytica.tools report rather than the legacy dune report
• Gauges can still be killed at any time due to externalities, the rules above are simply meant to keep the system lean and efficient.

Technical Specification

As pointed out above, the gauge removal list is generated by the data report from Defilytica https://balancer.defilytica.tools/gauge-kill-list.

The DAO Multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will interact with the AuthorizerAdaptorEntrypoint at 0xf5dECDB1f3d1ee384908Fbe16D2F0348AE43a9eA and call performAction using 0xab8f0945 for the data(bytes) argument and the “Gauge Address” list for each pool below will be used for the target(address) argument.