Balancer CEO proposes protocol wind-down and $9M+ treasury payout to BAL holders
A Snapshot vote runs Sept. 25–29, with a phased shutdown slated to start next month if approved.
Balancer Labs CEO Marcus Hardt has asked BAL holders to approve an orderly wind-down of the Balancer protocol and a pro-rata distribution of a remaining treasury worth more than $9 million. The proposal sets a Sept. 25–29 Snapshot vote and outlines a phased shutdown that would move the protocol toward withdrawal-only operations by Nov. 1 if tokenholders approve it.
Key Takeaways
- Balancer Labs CEO Marcus Hardt published a Sept. 15 governance proposal seeking approval to wind down the Balancer protocol and distribute a treasury worth more than $9 million to BAL holders on a pro-rata basis.
- The plan argues that Balancer v3 revenue has not scaled enough to replace legacy v2 revenue, leaving the protocol dependent on older fee streams despite post-exploit cost cuts and product delivery.
- DefiLlama figures cited in the proposal show monthly protocol revenue falling from $1.13 million in October to $371,000 in November after the November 2025 exploit, and reaching $56,781 in August 2026.
- BAL holders will decide the wind-down in a Sept. 25–29 Snapshot vote, with up to $400,000 earmarked to fund the shutdown process.
Hardt Puts a Full Balancer Wind-Down to BAL Holders
Balancer Labs CEO Marcus Hardt has put a full protocol wind-down in front of BAL holders, publishing a governance proposal on Sept. 15 that calls for an orderly shutdown of the Balancer decentralized exchange and automated market maker.
The proposal’s core trade is simple: approve a planned termination of operations and return the remaining treasury, described as worth more than $9 million, to BAL holders via a pro-rata distribution, or reject the plan and keep the current operating framework in place.
A Snapshot vote is scheduled for Sept. 25–29. Snapshot votes are off-chain governance polls that measure tokenholder support using balances at a specific block or time, and in practice they often function as the coordination layer for what the DAO will execute next.
Revenue Didn’t Come Back: v3 Still Hasn’t Replaced v2
Hardt’s rationale is framed as a revenue failure rather than a build failure. He wrote that Balancer’s post-exploit restructuring did what it was supposed to do on the cost and delivery side, but did not restore sustainable protocol income, which is the fees and other income captured by the protocol or DAO rather than what liquidity providers earn directly.
“What did not come was enough revenue. Most of the protocol’s revenue still comes from v2, and v3 revenue has not grown to replace it. The product worked. It did not sell enough,” Hardt said in a statement on X.
That distinction matters for governance because it narrows the set of plausible “turnaround” paths. If the issue is primarily product execution, tokenholders can credibly argue for more time and more shipping. If the issue is persistent revenue capture and adoption, the treasury becomes the central asset to defend, and the decision turns into whether to keep funding operations that have already been tried.
Hardt also tied the revenue problem to lingering adoption headwinds from the November 2025 exploit, even as Balancer v3 moved to a different architecture. “The November 2025 exploit hit legacy v2 pools. v3 is a different architecture, but the event followed the name into every conversation since and made traction harder to build,” he said on the Balancer forum. “I underestimated how much the exploit would continue to limit adoption,” he added in a separate post on X.
From the 2025 Exploit to 2026: The Revenue Slide in the Proposal’s Data
The proposal leans on a simple timeline: the exploit, then the revenue break, then a long grind lower that restructuring did not reverse.
Data from DefiLlama cited in the proposal show Balancer’s monthly protocol revenue at $1.13 million in October, then $371,000 in November after an exploit affecting composable stable pools on Balancer’s legacy v2. Hardt described the exploit as a $128 million event.
The cited figures then extend the story into 2026. DefiLlama data in the proposal put Balancer’s monthly protocol revenue at $56,781 in August 2026, a level that underwrites the wind-down argument: even if costs were cut, the revenue base being defended is small enough that the treasury can start to look like the only meaningful remaining pool of value for tokenholders.
Balancer Labs itself shut down in March 2026, with executives opting to continue operating the protocol under a leaner structure. The Sept. 15 proposal reads as the next step in that sequence, moving from “keep it running with fewer people” to “stop spending and return what’s left,” with governance now asked to formalize the endpoint.
Treasury Payout Design: $400K Wind-Down Budget and a May 2027 Burn-to-Redeem
If BAL holders approve the plan, the proposal calls for a phased shutdown to begin next month, though it does not specify an exact calendar date. New business development would end, and liquidity providers would have until Oct. 30 to prepare to exit.
Operationally, the proposal sketches two paths at the pool level. Pools that can be paused would move to a withdrawal-only state, meaning users can remove liquidity but cannot use the pool normally. Pools that cannot be paused would continue operating, but the protocol fee would be set to zero where contracts allow it.
From Nov. 1, the proposal says Balancer would operate only the minimal infrastructure needed to support withdrawals, and the DAO would be wound down with a small team managing the transition.
On the treasury side, the proposal sets aside up to $400,000 for the wind-down process, which reduces what ultimately gets distributed. The first pro-rata distribution is scheduled for May 2027 and uses a burn-to-redeem design: BAL holders would burn BAL in exchange for their share of treasury assets.
The proposal also outlines a second distribution that would return unspent wind-down funds and unclaimed assets from the first distribution, followed by a “final sweep” six months later. The exact date of the second distribution is not specified.
The immediate gating item is the Sept. 25–29 Snapshot vote, including whether governance discussion narrows or expands the wind-down scope and timeline. If the vote passes, the next practical test is whether the phased shutdown actually begins “next month” with a clarified start date, and whether pools begin shifting toward withdrawal-only states or fee-to-zero settings ahead of the Oct. 30 LP deadline. The Nov. 1 transition to “minimal infrastructure” is the other operational cliff, because it defines what users can realistically expect from the protocol beyond withdrawals.
My Read: BAL Governance Turns Into a Clock for LP Exits and Treasury Optionality
The filing is being read as a dramatic end, but the more actionable detail is that it turns governance into a schedule. The threshold that matters is whether BAL holders accept Hardt’s premise that the revenue problem is structural, not a temporary post-exploit dip, because that premise is what justifies protecting a $9 million-plus treasury rather than funding another year of operations.
The real test is whether the vote outcome forces pool behavior to change before any treasury distribution is even in sight, since the plan’s Oct. 30 and Nov. 1 milestones create deadlines that LPs and active users will front-run if they believe withdrawal-only states and fee changes are coming. If those operational steps land on time, the setup starts to look structural rather than narrative-driven, because the protocol’s remaining optionality shifts from “can revenue recover” to “how cleanly can the treasury be returned.”
