0x1ed28a141ed2…1ed28a17
Balancer Locks Oct. 30, Nov. 30 Wind-Down Dates After BAL Vote
Balancer will move pausable pools to withdrawals-only on Oct. 30 and pause its V3 Vault on Nov. 30 after BIP-928 approval, leaving $52.4M across V2 and V3 for holders to exit before treasury claims open in May 2027.
Outputs
$52.4M in liquidity remains across Balancer V2 and V3 pools per DefiLlama's Sept. 29 readings ($30.05M in V2, $22.31M in V3)
BIP-928 wind-down passed by BAL holders; separate fork proposal BIP-929 failed
Pausable pools move to withdrawals-only on Oct. 30; V3 Vault pauses Nov. 30; partners have until Oct. 16 to request V3 extensions
Managed treasury estimated at a minimum of $9M at proposal prices; first claim window opens end of May 2027 and runs six months
Holders must burn BAL to receive a pro rata share of eligible assets, paid in kind rather than in BAL
$52.4 million in liquidity remains across Balancer's V2 and V3 pools as the protocol locks in an orderly wind-down schedule following a BAL holder vote.
On Sept. 29, Balancer said pausable pools will shift to withdrawals-only on Oct. 30 and its V3 Vault will pause on Nov. 30. The dates follow the DAO's approval of BIP-928, a wind-down proposal that bundles protocol shutdown with treasury distribution. A separate fork proposal, BIP-929, failed.
"If you provide liquidity on Balancer, you can withdraw at any time, before or after these dates," Balancer told liquidity providers on X.
What does the shutdown actually change?
Pools that the protocol cannot pause keep running, with fees set to zero where their contracts permit. Balancer switches on recovery mode wherever needed to keep withdrawals open in paused pools. The shutdown dates are not withdrawal deadlines. The protocol reiterated that contracts are non-custodial and exits do not depend on the team continuing to operate.
Providers retain three exit paths: Balancer's front end, third-party tools, or direct on-chain transactions. The protocol will publish pool-specific treatment and migration guides before the Oct. 30 cutoff.
How large is the residual TVL?
DefiLlama's Sept. 29 readings, summed by The Defiant, show $30.05 million in V2 and $22.31 million in V3. The $52.4 million figure is a version-wide tally that includes pools scheduled to keep running as well as those headed for pause.
The split matters for partners negotiating extensions. Counterparties have until Oct. 16 to ask that named V3 pools stay live through Nov. 30. Extensions lengthen trading runway but do not lengthen bug bounty coverage, which terminates Oct. 30.
Who owns the treasury, and when do they collect?
BIP-928 valued the managed treasury at a minimum of $9 million at proposal-time prices. The plan retires an earlier BAL buyback and replaces it with a token-holder distribution. Proposal author Marcus Hardt wrote that V3 revenue had failed to replace V2 income despite a prior restructuring.
The first claim window opens at the end of May 2027 and runs for six months, through the end of November 2027. Holders must burn BAL to receive a pro rata share of eligible assets, paid in kind rather than in BAL. Only addresses that redeem in that first round qualify for a second-round airdrop of unspent funds and unclaimed assets. The mechanic routes residual value to participating redeemers, not back to the DAO.
What about locked tetuBAL positions?
TetuBAL holders, whose positions are permanently locked, will receive treasury BAL equal to 50% of the underlying amount measured at the original proposal's snapshot. They redeem in the same May-to-November 2027 window as other holders.
Balancer said the exact opening date will land at least two weeks ahead and warned that any site or direct message offering early redemption is fraudulent.
The defensible read for governance analysts: net asset value alone does not describe a holder's exit. The DAO sets the allocation formula, the payment assets, and the beneficiaries of any remainder. That pivot moves Balancer from an operating reserve model toward a one-time distribution governed by vote.
What comes next?
Balancer owes the market pool-specific migration documentation before Oct. 30. Partners evaluating V3 extensions face an Oct. 16 deadline. BAL holders wait until May 2027 for the first claim window, after the protocol discloses an audited distributable amount.
via x.com (Original)