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

[BIP-464] Remove BAL from Deprecated Ribbon Vault

Voting ended over 2 years agoSucceeded

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

Summary:

BIP-24 and BIP-227 permitted the DAO to initially deposit BAL into a Ribbon Finance vault, and then upsize the position. Recently, Ribbon has since decided to deprecate this covered call strategy vault, and it no longer will be a place for the DAO to earn passive income. The proposal is meant to enable the DAO to claim back the deposited funds to hold in the treasury.

Motivation:

As stated in the Summary, because this position will no longer be supported by Ribbon, the DAO should claim back these funds. Funds can be put to work elsewhere, but there is no sense in leaving them idle with nothing to be gained in the deprecated vault.

Specification:

The DAO Multisig 0x10A19e7eE7d7F8a52822f6817de8ea18204F2e4f will interact with the Ribbon Vault at 0x2a6B048eB15C7d4ddCa27db4f9A454196898A0Fe by writing initiateWithdraw passing numShares as 200000000000000000000000. This will take until the expiration of the next Ribbon round to register, at which time the BAL will be released for direct claim.

Upon release, the DAO Multisig will interact with the same Ribbon vault as noted above and write the completeWithdraw

The full payload cannot simulate due to the time dependence of the prior step. initiateWithdraw simulation Full transaction simulation with revert.

Off-Chain Vote

Yes, let's do it
3.69M veBAL100%
No, this is not the way
0.17 veBAL0%
Abstain
0 veBAL0%
Quorum:185%
Download mobile app to vote

Discussion

Balancer[BIP-464] Remove BAL from Deprecated Ribbon Vault

Timeline

Nov 01, 2023Proposal created
Nov 02, 2023Proposal vote started
Nov 06, 2023Proposal vote ended
Mar 16, 2026Proposal updated