[BIP-112] Adjust Balancer Snapshot for Aura AIP-17

Introduction

Aura was originally setup to allow each vlAURA to vote with its underlying share of veBAL. This required Aura voters to go to the Balancer Snapshot Space and vote. It also required separate delegation. The result was that much of the veBAL locked in auraBAL did not vote each round. Aura has recently passed an AIP to change how they handle veBAL voting, such that the AURA multisig will vote on snapshot with the veBAL in auraBAL following a snapshot vote of token holders. The governance can be found here:

https://snapshot.org/#/aurafinance.eth/proposal/0xe794b24a8c75914b29d9a09d61a549c33b0b50a95244b2d2bce4f8f425ee2d2e

This BIP proposes that balancer stop counting vlAURA as part of Balancer governance. Otherwise, Aura votes will be counted twice. Once if/when users vote of Balancer Snapshots, and once when the Aura multisig votes with all of veBAL.

Specification

• Change the Balancer Snapshot Voting to no longer include the aura-balance-of-vlaura-vebal strategy.
• Update the quorum on future votes to be 3 million veBAL.
• Extend all Balancer Snapshot votes by an additional 48 hours (120 hours in total) to provide AURA additional time to run a meta-snapshot. This will also ensure that balancer governance ends during the week in all timezones. -- Future snapshots will therefore start on Thursdays and end on Tuesdays.

Timing

AURA is ready to move forward with this new process. Given that it would be unfair for Aura to vote twice with their system owned veBAL, this BIP proposes to run an immediate vote to make a change to the snapshot space before any other votes are performed.

They will make the specified change for all other Balancer snapshot votes from now going forward. The Balancer Snapshot voting strategy should be changed before this, or vlAURA lockers will be able to vote on the balancer snapshot while auraBAL itself is also voting. This creates the possibility of votes being double counted.