Balancer is telling liquidity providers to pull their money out of its deprecated V1 pools immediately. The protocol said on Aug. 31 that it's aware of a bug that lets attackers drain LP funds, and the affected pools can't be paused.
Why the pools can't be paused
The V1 pools are non-pausable. That means the protocol has no switch to freeze them while a fix is deployed. So the burden falls on users — they have to move their own funds before someone else does.
Balancer's warning is blunt: withdraw from the legacy V1 pools. The company didn't say how many pools are affected or how much money is at risk, and it didn't name the bug or who found it. What's clear is that the usual safety net isn't there.
What LPs should do now
For anyone still holding positions in these pools, the instruction is to exit as soon as possible. There's no protocol-level pause coming to save them. The only line of defense is the liquidity provider's own action.
Balancer didn't give a deadline or say when a patch might land. It also didn't say whether any funds have already been stolen. The message is simply that the risk is live and the responsibility is on the user.
The legacy problem
V1 pools are old infrastructure. Balancer moved on to newer versions long ago, but some LPs never left. That's the audience for this warning — people who still have money sitting in a system that's no longer actively maintained.
Non-pausable pools are a design choice from an earlier era, one that assumed the protocol could always intervene. That assumption doesn't hold here. So the protocol is asking users to be the emergency brake.
What happens next is up to the LPs. The clock is running, and there's no word yet on whether Balancer will offer compensation or a migration path. For now, the only concrete step is to withdraw.
