Balancer's $1.39M Recovery Lacks Claim Data

Balancer's proposal to return $1.39 million in stolen funds to liquidity providers is stuck because it does not yet say who gets what. The plan divides 296.401711 ETH among 120 legacy V1 pools, but as of September 20, the forum post lacks a vote link, a claim window, and the per-address data needed to calculate a payout (source: fact:F5, article).

The snapshot timing drives the allocation. Balancer bases each provider's share on pool-token holdings at Ethereum block 25,872,248, a point "immediately before the first exploit transaction at block 25,872,249" (source: fact:F4). Five ETH returned to the DAO Multisig between September 8 and September 16, yet the proposal records 296.401711 ETH as the total recovered amount, not a promise of full reimbursement (source: fact:F3, article).

The vulnerability belongs to a recurring family. A rounding error in how the protocol calculates token amounts during a swap allowed an attacker to drain $116 million from Balancer's V2 pools last November (source: source:F2). That prior incident established the technical category of the flaw, but the current recovery remains procedural rather than operational.

Balancer V3 now holds about $29.4 million in total value locked, down sharply from more than $400 million at its 2025 peak (source: source:F1). The protocol is also proposing a wind-down, which preserves recovered exploit funds for LPs outside the treasury distribution intended for BAL holders (source: article). The Sept. 18 post "does not include the per-pool allocation table, holder lists or per-address amounts" (source: article). Until that data appears, the recovery defines a route, not a confirmed payout (source: article).