Balancer Considers Wind-Down After Restructuring Doesn’t Restore Revenue

Balancer, one of the best-known decentralized exchanges built on automated market makers, has proposed winding down its protocol after a post-exploit restructuring failed to restore enough revenue to sustain growth. Balancer Labs CEO Marcus Hardt said he underestimated how long the fallout from a $128 million exploit in November would continue to suppress user traction.

The plan, posted on Balancer’s governance forum on Monday by Hardt, calls for a phased shutdown and the distribution of a remaining treasury currently valued at more than $9 million to BAL tokenholders. The proposal follows Balancer Labs’ earlier decision to shut down in March, when the team moved to a leaner operating structure while still supporting the protocol.

Key takeaways

• Balancer’s governance proposal would transition the protocol into a withdrawal-focused end state and wind down the DAO.
• The plan attributes weak revenue recovery to continued adoption drag after a November $128 million exploit tied to legacy v2 stable pools.
• Balancer Labs previously restructured to cut costs, but Hardt said the revenue side of that strategy fell short—v2 revenue declined and v3 did not replace it.
• The treasury distribution is expected to begin in May 2027, with additional rounds of payouts and a final sweep months later.
• BAL holders will vote on the wind-down via a snapshot window scheduled for Sept. 25–29.

Why Balancer is moving toward a shutdown

Hardt’s proposal positions the wind-down as the next step after a cost-focused overhaul. According to Hardt, Balancer Labs’ March shutdown and leaner follow-on structure achieved the promised operational changes—reducing costs and delivering certain products to tokenholders—but did not generate sufficient revenue to justify continuing full development and business support.

In a statement on X, Hardt argued that “most of the protocol’s revenue still comes from v2,” while v3 revenue had not grown enough to fill the gap. He summarized the outcome as a product that worked but did not “sell enough,” framing the issue less as a technical failure and more as an economic one.

Hardt tied the revenue weakness to the long tail of the November exploit. Data from DefiLlama shows Balancer’s monthly protocol revenue dropping sharply following the incident: it fell to $371,000 in November from $1.13 million in October. DefiLlama data also indicates revenue continued to trend downward into 2026, with August revenue at $56,781.

While the exploit impacted legacy v2 composable stable pools, Hardt emphasized that the incident’s name and reputational impact still carried into v3 discussions and made it harder to build traction. In his governance forum post, he said the November 2025 exploit “hit legacy v2 pools,” noting that v3 uses a different architecture—but added that he underestimated “how much the exploit would continue to limit adoption.”

How the proposed wind-down would work

The governance document outlines a staged approach beginning next month. It would end new business development immediately, and it would give liquidity providers until Oct. 30 to prepare to exit the protocol. In the meantime, the plan distinguishes between pools based on whether they can be paused.

Pools that can be paused would be moved to withdrawal-only. For pools that cannot be paused, they would continue operating, but—where contracts allow it—the protocol fee would be set to zero. This structure aims to preserve user exit paths while reducing ongoing protocol economics that could further drain the treasury.

From Nov. 1, Balancer would run only the minimal infrastructure needed to support withdrawals, and the DAO would be wound down with a smaller team handling the transition. The proposal sets aside up to $400,000 specifically for the wind-down process.

Treasury distribution plan for BAL holders

Under the proposal, BAL holders would receive the remaining treasury on a pro-rata basis. The first distribution is scheduled for May 2027, at which point holders would burn their BAL in exchange for their share of the treasury assets.

Hardt’s plan also includes follow-on steps: a second distribution would return unspent wind-down funds and unclaimed assets from the first distribution, followed by a “final sweep” six months later. The governance process also anticipates operational wind-down costs, which would be drawn from the allocated budget.

Hardt argued against delaying the shutdown, saying that continuing on the current path would spend treasury resources without changing the eventual outcome. In his view, the central question is whether the remaining treasury stays substantial enough to reach holders, rather than being depleted by additional costs on a timeline that has already been tested.

Governance vote and what happens if it fails

The wind-down requires approval from BAL holders. The proposal specifies a snapshot vote scheduled for Sept. 25 to 29. If tokenholders reject the plan, Balancer would remain on its existing operating framework, meaning the protocol would not transition into the withdrawal-focused shutdown described in the proposal.

Until that vote, the key uncertainty for market participants is whether the governance process reflects tokenholder appetite for returning remaining assets sooner—or confidence that revenue recovery can be achieved without winding down.

With Balancer’s revenue already showing a prolonged decline after the November exploit, traders, liquidity providers, and developers will likely watch the snapshot outcome closely—not only for the immediate operational changes, but for what the decision signals about how DeFi protocols decide between continued restructuring versus full decommissioning when adoption fails to rebound.