Balancer proposes orderly shutdown and BAL treasury split

Balancer’s September 14 proposal would stop funded protocol operations, preserve contract-level withdrawals and convert BAL into a time-limited claim on the DAO treasury if token holders approve it. Nothing has shut down: a Snapshot vote is scheduled for September 25–29, with a 5 million BAL quorum. For builders, the immediate change is notice. Integrations should plan liquidity migration and direct-withdrawal support before October 30, while teams seeking the code, licences or deployments would need separate governance votes to carry them forward.

What would Balancer’s wind-down change?

The plan would retire Balancer’s operated product layer without pretending its non-custodial contracts can simply be switched off. On October 30, pools that support pausing would move to withdrawals only; recovery mode would be enabled where required to keep exits open. Pools that cannot be paused would continue under their existing rules, with protocol fees set to zero where possible. From November, a reduced stack would keep a withdrawal interface, necessary subgraphs, documentation and the veBAL unlock path available.

• New business development and the current frontend routing would end.
• Admin, multisig and emergency roles would be revoked or transferred in stages.
• Bounty coverage would end on October 30; open reports would still be resolved.
• Recovered exploit funds would remain reserved for affected liquidity providers.

That is a sunset of maintained infrastructure, not deletion of deployed code. It also exposes the practical meaning of “immutable”: users can still call contracts, but indexing, routing, interfaces and incident response all consume resources that somebody must fund.

How would BAL holders receive the treasury?

Holders would burn BAL during a six-month window beginning at the end of May 2027 and receive a pro-rata basket of the assets actually held by the treasury. The denominator would exclude BAL held by the treasury and specified Balancer Labs safes. The opening block would fix balances and eligibility, and the proposal says the treasury—estimated at no less than $9 million at current token prices—would be inventoried and audited before claims open.

A second, automatic distribution would send unspent budget, late revenue and the unclaimed portion to addresses that redeemed in round one, weighted by the BAL each burned. A final sweep would follow six months later. This rewards attentive claimants but makes the deadline consequential: a passive holder who misses round one loses both the initial redemption and every later distribution. Wrapper holders must also unwind into BAL in time, except for the proposal’s special handling of immutable tetuBAL.

Does the economics justify shutting Balancer down?

The economics support a wind-down more strongly than they support another open-ended turnaround. The proposal reports an all-in burn of about $150,000 a month, against roughly $30,000 of protocol revenue in August and about $25,000 of monthly treasury income. Its wind-down cap is $400,000: $150,000 through May 2027, $30,000 afterward and a $220,000 contingency reserve. Unspent funds return to holders. Continuing at the current run rate consumes roughly that entire cap in less than three months.

The strongest alternative is a separately funded fork that preserves Balancer’s pool technology without making the treasury absorb another growth bet. The weakness is sequencing: token holders are asked to approve allocation rules before the claim contract and implementation specification are published, with that specification due by February 2027 and an audit only promised before launch. The verdict is therefore split but clear: retiring the operated protocol is economically credible, and permissionless code can outlive the organization; treasury execution should remain gated on a published, audited contract and a complete asset inventory. Until the vote passes, this is a proposal, not a payout or shutdown.