Balancer is winding down. LPs now have two exit clocks to watch
Balancer holders approved a phased wind-down. Pool restrictions and security coverage change October 30, while some v3 pools may run until November 30.
Article
Balancer is winding down, but it is not switching off in one moment.
Token holders approved BIP-928 with about 99.19% of the recorded vote supporting one of the two “yes” options. The result gives liquidity providers two important dates: October 30 and November 30.
The simple version is that withdrawals stay open. What changes is how long normal pool activity and security coverage continue.
The first clock is October 30
A liquidity pool is a shared pot of tokens used for swaps. The people who supply those tokens are liquidity providers, often shortened to LPs.
On October 30, Balancer plans to pause pools that can be paused and move them to withdrawals-only. Pools that cannot be paused can keep working, but protocol fees will be set to zero where the contracts allow it.
The bug-bounty program also ends that day. This matters even for a v3 pool that receives extra time. The pool may remain active, but the same bounty coverage will not remain with it.
The Defiant highlighted that split between continued withdrawals and the end of coverage:
Balancer’s approved wind-down moves pausable pools to withdrawals-only on October 30, while withdrawals remain open.
The Defiant (@DefiantNews) · September 29, 2026
The second clock is November 30
Some v3 pools can receive one extra month. A partner must ask by October 16, and Balancer plans to publish the qualifying list before October 30.
Those selected pools may continue until November 30, when the v3 Vault is scheduled to pause. Withdrawals should remain possible throughout.
That does not mean every v3 pool automatically gets extra time. LPs need the final pool list, not only the broad announcement.
BAL holders have a much longer clock
The vote also cancels the old BAL buyback plan. Instead, eligible holders are scheduled to get a six-month redemption window starting around the end of May 2027.
The planned mechanism burns eligible BAL and gives each redeemer a proportional share of treasury assets. In September, the proposal author measured about $9.96 million of distributable non-BAL assets, equal to roughly $0.1579 per redeemable BAL at that moment.
That number is not a guaranteed price. Treasury assets can rise or fall, operating costs can change, recoveries may arrive, and the final eligible supply is measured later. The opening snapshot and claim contract also still need to be specified and audited.
What LPs and holders should check
- LPs: identify the exact pool and whether it receives the v3 extension.
- Anyone relying on bounty coverage: October 30 is the important date, even if a pool keeps running.
- BAL holders: treat $0.1579 as an old measurement, not a promised payout.
- Everyone withdrawing: use verified interfaces or contract instructions and check pool-specific conditions.
The vote settled the direction. It did not remove the need to watch the implementation.
Sources and reporting notes
Checked September 30, 2026. The schedule, withdrawal language, cancelled buyback and redemption design come from BIP-928. The final vote weights were retrieved from Snapshot’s public GraphQL result for the proposal. The selected X post is independent reporting, not proof that every implementation step has occurred.
We did not verify a completed pool migration or withdrawal. The final partner-pool list and May 2027 redemption implementation were not yet available. This article explains deadlines and risks, not whether anyone should buy, hold or sell BAL.