Balancer will begin winding down its operations after BAL holders approved a proposal to shut the decentralized exchange. The protocol announced the shutdown dates on Sept. 29, with the first service restriction coming at the end of October.
Pausable pools will move to withdrawals-only mode on Oct. 30, meaning liquidity providers can pull funds out but no new deposits or swaps will be processed. The V3 Vault, which handles the protocol's core accounting, will pause on Nov. 30.
What BAL holders approved
The wind-down was authorized through BIP-928, a governance vote that also covered how the protocol's treasury will be distributed. The proposal passed, giving the green light for the staged shutdown. A separate proposal, BIP-929, deals with a fork of the protocol, though the announcement did not specify what that fork entails or who is behind it.
The approval ends months of uncertainty for a project that once ranked among the largest automated market makers. The two-stage timeline gives users roughly a month between the withdrawals-only transition and the Vault pause to remove assets. Pausable pools are those that can be halted by the protocol's governance or emergency mechanisms; not all pools fall into that category, but the V3 Vault pause will affect the broader system.
Withdrawals-only on Oct. 30
Starting Oct. 30, pausable pools will stop accepting new liquidity and will not process trades. Users can still withdraw their funds, but the pools will effectively become read-only. This is a common first step in DeFi wind-downs, designed to prevent new capital from entering a protocol that is being shut off.
The withdrawals-only phase is not a full freeze. It's a controlled exit for liquidity providers who need to reclaim tokens. The protocol has not said whether any pools will remain active beyond the pausable set.
V3 Vault pause on Nov. 30
The harder stop comes on Nov. 30, when the V3 Vault is paused. The Vault is the central component that tracks balances and settles transactions across the protocol. Pausing it effectively halts all remaining on-chain activity that depends on the Vault, including any pools that were still operational.
After that date, the protocol's smart contracts will still exist on-chain, but the Vault pause will prevent normal use. Users who miss the deadline may need to rely on direct contract interactions or any fork that emerges from BIP-929. The treasury distribution outlined in BIP-928 will also proceed, though the announcement did not give a specific schedule for those payouts.
What BIP-929 means for a fork
BIP-929 is the wildcard. The proposal relates to a fork, but the announcement offered no details on its scope, leadership, or whether it will preserve the Balancer codebase. In DeFi, forks often emerge when a community wants to continue a project after the original team or governance votes to shut down. It's unclear whether BIP-929 has passed or is still pending.
For now, the official Balancer timeline is set: withdrawals-only on Oct. 30, Vault pause on Nov. 30. Anyone holding assets in pausable pools or using the V3 Vault has until those dates to act. The fork proposal remains an open question that could determine whether the Balancer name lives on in a new form.
