• © Goverland Inc. 2026
  • v1.0.5
  • Privacy Policy
  • Terms of Use
BalancerBalancerby0x9f74662aD05840Ba35d111930501c617920dD68eveballer.eth

[BIP-481] Claim and Lock Balancer DAO Aura allocation into vlAura

Voting ended over 2 years agoSucceeded

Payload with PR: https://github.com/BalancerMaxis/multisig-ops/pull/618 Summary:

Back when Aura launched, a portion of the supply was allocated to the Balancer DAO. That vested Aura exists in the following vesting contract: https://etherscan.io/address/0xfd72170339ac6d7bdda09d1eaca346b21a30d422#code We are proposing to lock the 1.4m aura that has been vested.

Motivation:

At the time of writing, 1.4m Aura has vested with 600k Aura left unvested. We are proposing to lock this into vlAura to begin earning rewards and eventually start allocating vote weight towards revenue generating or strategically important pools that lack a proper means of bootstrapping without ecosystem stakeholders voting philanthropically. A proposal for how the DAO will deal with allocating this vlAura voting power will be presented in the coming weeks, but we think it is prudent to initiate the locking now.

Specification:

The DAO multisig on mainnet 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will call the claim() function on the AuraVestedEscrow at 0xfd72170339ac6d7bdda09d1eaca346b21a30d422 with the parameter _lock set to true.

Off-Chain Vote

Yes, let's do it
3.96M veBAL100%
No, this is not the way
0.43 veBAL0%
Abstain
474.5 veBAL0%
Quorum:198%
Download mobile app to vote

Discussion

Balancer[BIP-481] Claim and Lock Balancer DAO Aura allocation into vlAura

Timeline

Nov 08, 2023Proposal created
Nov 09, 2023Proposal vote started
Nov 13, 2023Proposal vote ended
Feb 16, 2026Proposal updated