# [BIP-928] Orderly Winddown of Balancer and Distribution of the Treasury

- Space: [Stake DAO BAL](https://snapshot.box/s:sdbal.eth.md)
- Author: 0xb4542526AfeE2FdA1D584213D1521272a398B42a
- State: Closed
- Voting type: Weighted
- Start: 2026-09-25 18:24 UTC
- End: 2026-09-28 18:24 UTC
- Votes: 5
- Quorum: 32,331.2 voting power
- Open in Snapshot: https://snapshot.box/#/s:sdbal.eth/proposal/0x25b4dd13e0119ed57a8b3cfc01df7df14e7ed9bd3437fd5375c3cfc46eb93671

## Results

- Yes, with tetuBAL at 50%: 0 voting power, 0.0%
- Yes, with tetuBAL at 100%: 157,261.86 voting power, 93.6%
- No: 10,832.78 voting power, 6.4%
- Abstain: 0 voting power, 0.0%

## Proposal

> How this vote is counted. - The two Yes options are added together: the proposal passes if their sum is greater than No, with quorum counted over all votes cast. Between the two Yes options, the one with more votes sets the tetuBAL fraction; if they tie, it is 50%.

## TL;DR

- I propose an orderly winddown of Balancer: no new business development, a phased sunset of the protocol with a defined exit window, and the DAO closed to the extent legally and practically possible.
- The treasury goes to BAL holders in kind and pro rata, after setting aside what the winddown still needs to spend, in two rounds and a final sweep. Round one opens at the end of May 2027: holders burn their BAL and receive their share of the treasury. Round two is an airdrop to the addresses that redeemed in round one, in proportion to what they redeemed, within two months of the close: the unspent budget, what arrived since, and the share not redeemed. A final sweep six months later distributes anything that arrives after that, to the same addresses.
- The treasury is at least $9M at current token prices, the managed treasury [reported by kpk](https://balancer.octav.fi/app/balancer-treasury); the full inventory of DAO addresses and positions is published in this thread. The figure that counts is measured and audited at the block round one opens. BAL, and anything that resolves into BAL, is excluded, other than the BAL that goes to tetuBAL holders. The [BIP-919](https://forum.balancer.fi/t/bip-919-bal-tokenomics-revamp/7001) buyback is cancelled.
- Contributor notice runs to 31 October 2026. Pools move to withdrawals only, where the contracts allow it, on 30 October 2026. v3 pools that partners ask to keep running stay live until 30 November 2026.
- This vote approves the direction, the timeline, what happens to what the DAO owns beyond the treasury, the distribution of the treasury to BAL holders including every allocation rule below, a winddown budget of $150k from 1 November 2026 to May 2027, $30k from then to the final sweep, and a reserve of $220k drawn only if needed, replacing the remaining BIP-918 allocation from that date. It also cancels the BIP-919 buyback and supersedes [BIP-687](https://forum.balancer.fi/t/bip-687-transition-of-bug-bounty-program-responsibility-to-balancer-dao/5847).
- The Snapshot has two Yes options, which differ only in the tetuBAL fraction: 50% or 100%. Both count as Yes; the one with more votes sets the fraction.
- Spending to 31 October, including the contributor notice, runs under BIP-918 and is not part of this vote. What is left of that allocation is not carried over as a new budget: it is spent down against the winddown budget below, and whatever remains returns to the treasury.
- The mechanism that implements the distribution is published as an implementation specification, for comment, not for a vote. Transferring anything the DAO owns beyond the treasury, such as code, licences or deployments, gets its own Snapshot vote. Any change to an allocation rule comes back to a vote.

## Motivation

Balancer tried. In April, token holders approved a plan to take the protocol to profitability on a restructured base: costs cut, emissions ended, the token model simplified, protocol revenue routed to the DAO, growth expected from v3. They backed it, and the team executed it. v3 is live and operating as designed. Boosted Pools remain a category Balancer defined. AutoRange Pools shipped, the product expected to get us there. New integrations and partnerships were pursued throughout. Some generated interest. None converted into sustained revenue growth. Key people left or stepped back over that period, and the plan ran with less than it was designed with.

The revenue picture is why this comes now. Most of the protocol's revenue still comes from v2. v3 revenue has not grown to replace it. [BIP-918](https://forum.balancer.fi/t/bip-918-operational-restructuring-for-balancer/7000) set a review for exactly this case. This proposal is that review, brought early. Waiting for the calendar would change the numbers, not the conclusion, and every month of waiting is spent from the treasury.

The November 2025 exploit hit legacy v2 pools. v3 is a different architecture, but the event followed the name into every conversation since and made traction harder to build. It is part of why the plan was harder than it looked in April; it is not what this rests on. With a working product suite, a lean structure and full effort from everyone who stayed, the traction the plan required did not come. I do not see a funded path that changes this picture.

Continuing on the current path spends the treasury to arrive at the same place later. That treasury belongs to BAL holders. The question is whether what remains reaches holders while it is still substantial, or is spent first on a path that has already been tried.

## Specification

This vote approves the following package. Communication changes from this post; winddown actions wait for the vote.

1. **The protocol sunsets in phases.** The contracts are non custodial: withdrawing does not depend on Balancer or on anyone continuing to operate. Every step is announced before it happens.
   - **Exit window, from this post.** Documentation for withdrawing directly from the contracts, and through third party tools that already support it, is published in this window.
   - **Withdrawals only, on 30 October 2026.** This proposal is the notice. On that date, pools that can be paused are paused and move to withdrawals only; pools that cannot be paused keep working, with the protocol fee set to zero where the contracts allow it. The exception is v3 pools that a partner asks to keep running so it can migrate: requests come in by 16 October, the list is published before 30 October, and those pools stay live until 30 November, when the v3 Vault is paused. Where a pool's contracts require it, recovery mode is enabled when it is paused, so withdrawals stay open. Pools differ; the treatment of each is published before 30 October. After these dates the protocol does not depend on Balancer operating it, and the frontend, routing and communication treat it as discontinued.
   - **Minimal infrastructure.** From 1 November, infrastructure steps down to what the v3 pools kept running need until 30 November, and then to a simplified withdrawal interface, the subgraph coverage it needs and public documentation, kept available, including the veBAL unlock path, until the veBAL locks expire and through both distribution rounds.
   - **Permission cleanup.** Admin permissions, multisig roles and remaining privileged access, including the mainnet DAO multisig and the Emergency subDAO, are inventoried, then revoked or transferred as each becomes safe to retire. Permissions relevant to veBAL unlocks are retired only after the end of May 2027; control of the treasury and the distribution contracts only after the distribution process ends. The end state is a protocol that needs no one from Balancer: the DAO gives up its own privileged roles. Roles that cannot be removed are inventoried and published.

2. **Contributor notice and winddown budget.** Contributors were given two months of notice on 27 August, running to 31 October, a management decision within the approved budget. Spending to 31 October, including the notice, runs under BIP-918 and is not part of this vote. From 1 November, this proposal's winddown budget applies: $150k to May 2027, $30k from then to the final sweep, and a reserve of $220k drawn only if needed. It replaces the remaining BIP-918 allocation from that date and is a cap, not a transfer: what is already funded at the OpCo is spent first, and only the balance is drawn. A small transition team on an hourly basis, sized to what the winddown needs, does the remaining work, coordinated by the OpCo. Whatever is not spent returns to the treasury and goes into the distribution.

3. **What the DAO owns beyond the treasury.** Code, licences, deployments and the like are disposed of by governance, each transfer through its own Snapshot vote. Nothing is handed to anyone by default. Value realized from any of it flows to the treasury. What belongs to the DAO and what sits with the legal entities is established before any such vote. Existing obligations to counterparties are honored through the transition or wound down explicitly with each of them, not dropped. Whatever finds no operator stays open source, with documentation and archives published.

4. **The BIP-919 buyback and the BIP-687 earmark.** BIP-919 committed the DAO to a voluntary BAL buyback at NAV, capped at 35% of the treasury at that Snapshot, opening twelve months after it. This proposal cancels that buyback and replaces it with the distribution in item 7. The veBAL compensation in the April package was paid in May under [BIP-920](https://forum.balancer.fi/t/bip-920-vebal-compensation-airdrop/7025) and is not affected. BIP-687 ring fences $1M USDC for the bug bounty program. This proposal supersedes it: the earmark is released when coverage ends and the reports open at that date are resolved.

5. **Bug bounty.** Coverage runs through the exit window and ends on 30 October 2026, the withdrawals only date. 

6. **Consolidation before round one.** Funds in other DAO wallets and sources, including operational safes and fee collection wallets, are consolidated into the Treasury Safe. Open receivables and unclaimed positions in the DAO's name are recovered. The base reflects everything the DAO holds and is owed, net of what belongs to others, not only what sits in one safe today.

7. **Treasury distribution.** This vote decides it. In kind, in the tokens actually held, pro rata, in two rounds.
   - **Base:** measured at the opening snapshot, the block at which round one opens, announced at least two weeks ahead, and audited. The treasury is at least $9M, estimated at current token prices. That is the managed treasury [reported by kpk](https://b...

---

To vote or create proposals from an AI assistant, connect the Snapshot MCP at https://mcp.snapshot.box

