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

[BIP-454] Claim Second SAFE Airdrop

Voting ended over 2 years agoSucceeded

PR With Payload

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

Tenderly Simulation

https://dashboard.tenderly.co/public/safe/safe-apps/simulator/c1c80f66-050b-4f82-94d2-c97ab868079a

Motivation

The passing of Safe DAO's SEP-5 resulted in new allocations for existing $SAFE holders. The Balancer DAO multisig is such a holder.

Urgency

NOTE: in order to successfully claim this second airdrop, the vesting needs to be created before 2023-10-27T10:00:00 UTC (ref)!

Specification

Payload consists of three calls:

  • Airdrop2.redeem: this creates a vesting for the msg.sender
  • Airdrop2.claimVestedTokensViaModule: this claims the $SAFE tokens already vested. By passing a max(uint128) we claim all available tokens
  • Airdrop1.claimVestedTokensViaModule: idem, but claim pending tokens from the vesting created during the initial airdrop

This results in two transfers to the multisig totalling to roughly 2000 $SAFE.

Off-Chain Vote

Yes, let's do it
3.72M veBAL100%
No, this is not the way
0.05 veBAL0%
Abstain
0.14 veBAL0%
Quorum:186%
Download mobile app to vote

Discussion

Balancer[BIP-454] Claim Second SAFE Airdrop

Timeline

Oct 19, 2023Proposal created
Oct 19, 2023Proposal vote started
Oct 23, 2023Proposal vote ended
Mar 02, 2026Proposal updated