[BIP-316] Replace veBAL Gauge

Voting ended almost 3 years agoSucceeded

https://github.com/BalancerMaxis/multisig-ops/pull/233

Motivation

The current veBAL gauge directs emissions to a recipient, then the emissions must be withdrawn and deposited to the fee distributor. This is a permissioned action that can be deprecated by utilizing the latest singleRecipientGauge factory which has the capability to deposit tokens directly into the fee distributor. Once this new gauge is added to the checkpointer the process of distributing BAL emissions to veBAL will be fully automated.

Specification

The DAO Multisig eth:0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will interact with the AuthorizerAdapterEntryPoint 0xf5dECDB1f3d1ee384908Fbe16D2F0348AE43a9eA with the following arguments:

target: 0xE867AD0a48e8f815DC0cda2CDb275e0F163A480b which corresponds to the veBAL gauge data: 0xab8f0945 which corresponds to the function for kill()

The Balancer Maxi LM Multisig eth:0xc38c5f97B34E175FFd35407fc91a937300E33860 will interact with the GaugeAdderv4 at 0x5DbAd78818D4c8958EfF2d5b95b28385A22113Cd and call the addGauge function with the following argument:

gauge: 0xb78543e00712C3ABBA10D0852f6E38FDE2AaBA4d which corresponds to the new 10% capped gauge for veBAL

gaugeType: EthereumSingleRecipientGauge

Off-Chain Vote

Yes, let's do it

8M vlAURA100%

No, this is not the way

19.43 vlAURA0%

Abstain

50 vlAURA0%

Download mobile app to vote

Discussion

[BIP-316] Replace veBAL Gauge

Timeline

Jun 01, 2023Proposal created

Jun 01, 2023Proposal vote started

Jun 05, 2023Proposal vote ended

Jan 17, 2025Proposal updated