Balancer’s 296 ETH recovery lacks vote and payout details for affected LPs

Balancer’s DAO published a Sept. 18 proposal to distribute 296.401711 ETH recovered after an Aug. 31 exploit of its V1 pools, but the document does not yet tell any liquidity provider what they would actually be paid. That gap between “recovery” and “reimbursement” matters to institutional LPs weighing how DeFi protocols handle post-hack governance, legal exposure and payout timelines.

• Balancer recorded 296.401711 ETH returned to its DAO multisig against $1.39 million in tokens drained at attack-time prices.
• Five separate ETH transfers arrived between Sept. 8 and Sept. 16 from the main grey hat, three anonymous white hats and block builder Ultrasound.money.
• As of Sept. 20 the proposal remained labeled BIP-XXX with no Snapshot vote link, and no per-address claim amounts have been published.

• 296 ETH total recovered and returned to the Balancer DAO multisig
• $1.39M value of tokens drained at attack-time prices on Aug. 31
• 120 legacy V1 pools eligible to share the recovered ETH

Balancer’s DAO wants to split the recovered 296.401711 ETH among liquidity providers across 120 legacy V1 pools hit in the Aug. 31 exploit, according to the proposal posted to the Balancer forum. The plan sets out a formula for dividing the ETH but stops short of showing what any specific address would receive.

Five Transfers From Grey Hat and Ultrasound.money Built the 296 ETH Pool

The proposal traces the 296.401711 ETH to five separate returns made to the Balancer DAO multisig between Sept. 8 and Sept. 16. The main grey hat behind the recovery, three anonymous white hats and block builder Ultrasound.money each contributed a portion of the total.

That figure represents what came back, not what was taken. The proposal values the original drain at roughly $1.39 million in tokens priced at the time of the attack, while the recovery pool is denominated entirely in ETH.

Because the loss is expressed in historical dollars and the recovery is expressed in current ETH, the document does not state a recovery percentage. An LP cannot tell from the proposal alone what share of their original loss the 296.4 ETH is meant to cover.

Allocation Formula Locks In a Pre-Attack Block, Not Live Balances

Under the plan, Balancer would first split the recovered ETH across the 120 pools based on each pool’s share of the total dollar loss at attack time. It would then divide each pool’s allocation among liquidity providers according to their pool-token holdings at Ethereum block 25,872,248, the block immediately preceding the first exploit transaction at block 25,872,249.

Using a single pre-attack snapshot lets Balancer cover all 120 pools with one formula, including pools later hit by copycat exploit attempts. The approach standardizes eligibility but adds a step LPs must still wait on.

The Sept. 18 forum post does not include the per-pool allocation table, holder lists or per-address amounts that the formula requires to produce a real number. Until Balancer publishes those files, no liquidity provider can calculate an exact ETH payout, even after doing the math on the formula itself. The mechanics of tracing DeFi risk after an exploit echo the broader trust gap explored in CryptoCoinShow’s look at why smart contracts still struggle to verify real-world conditions.

Legal Release and Unscheduled Snapshot Vote Stand Between LPs and Cash

Accepting any eventual payment carries a condition beyond the math. Claimants would have to provide digital consent releasing Balancer Labs, Balancer DAO, Balancer Foundation, affiliated parties and service providers from liabilities tied to the incident.

Payments would be made in ETH, while claims tied to smart contracts or multisig wallets would be handled case by case rather than through the standard formula.

As of Sept. 20, the proposal still carried its placeholder BIP-XXX label and included no Snapshot vote link, leaving the governance step that would trigger a payout unscheduled. The post states that claim data and a claim mechanism would only be published and deployed if the proposal passes, with no announced start or end date for the V1 claim window. That timeline sits apart from Balancer’s separate wind-down proposal, which specifies that funds recovered from protocol attacks belong to affected LPs and sit outside the treasury distribution earmarked for BAL holders.

The CCS read. For institutional LPs, the real signal here is process risk, not amount. A recovery that requires a legal release, an unpublished holder list and an unscheduled Snapshot vote before a single ETH moves sets a template other DeFi protocols will likely copy after their own exploits, for better or worse. Capital allocators comparing DeFi exposure to structures like the underwriter-capital growth tracked at Cap should weight this governance lag into their risk models.

The next concrete step is procedural: Balancer’s DAO must attach a Snapshot vote link to the still-placeholder BIP-XXX proposal before per-pool allocation tables, holder lists or a claim mechanism can be published, and no date for that vote has been set as of Sept. 20.