PR with Payload
Summary
The Balancer DAO has locked its vested AURA into vlAURA with [BIP-481]. The first lock of 1.42m AURA will expire and can be relocked after March 7th and before the unlolck date of March 14th, 2024:
The DAO wishes to relock its current position and bundle it with an additional vest so the next unlock is bundled into one in 16 weeks from the relock date.
Motivation
The Balancer DAO wishes to relock its vlAURA position to continue to vote for Balancer gauges with its position. To do so the DAO needs to relock its expired position timely after March 7th and before March 14th 2024
At the time of writing, the DAO is entitled again to roughly ~280k AURA tokens (can be verified by calling available with _recipient as 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f Aura: Vesting to Balancer | Address 0xfd72170339ac6d7bdda09d1eaca346b21a30d422 | Etherscan ). Another ~297k AURA remains unvested and will be claimed at a later date.
We are proposing to initiate another lock with the available ~280k AURA to be used to vote on AURA governance. The specifics of the Balancer DAOs voting allocations can be found here.
By re-locking the initial position and vesting additional AURA between March 7th and March 14th which would fall into the same locking epoch, it is guaranteed that the entirety of the locks will be up for re-lock in 16 weeks, reducing load on the multi-sig, streamlining the management of this position.
Specification
The Balancer DAO Multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will interact with the vlAURA contract at 0x3fa73f1e5d8a792c80f426fc8f84fbf7ce9bbcac and call processExpiredLocks with argument true - The execution needs to be timed AFTER March 7th and BEFORE March 14th
Additionally, the DAO multisig on mainnet 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will call the claim function on the AuraVestedEscrow at 0xfd72170339ac6d7bdda09d1eaca346b21a30d422 with the parameter _lock set to true. This execution, as well as the above, needs to be timed AFTER March 7th and BEFORE March 14th
