Balancer proposes dividing ETH recovered from an August exploit across 120 V1 pools
CryptoSlate reports Balancer would divide 296.401711 ETH returned after an Aug. 31 exploit among LPs in 120 legacy pools, but no claim window is open yet.
Why it matters
Because the loss is stated in historical dollars and the recovery pool in ETH, with no recovery percentage given, what any individual address receives is not yet determinable. Until a vote passes and address-level claim data is published, liquidity providers in the 120 affected pools have no route to redeem the returned ETH.
Key facts
A Balancer V1 recovery proposal would divide 296.401711 ETH returned after an Aug. 31 exploit among liquidity providers in 120 legacy pools.
296.402 ETHReported by CryptoSlate
The proposal records that tokens worth about $1.39 million at attack-time prices were drained from the pools.
Reported by CryptoSlate
Recovered ETH would be allocated to each pool by that pool's share of the total dollar loss at the time of the attack, then divided among liquidity providers by pool-token holdings at Ethereum block 25,872,248.
Reported by CryptoSlate
Ethereum block 25,872,248 immediately preceded the first exploit transaction at block 25,872,249.
Reported by CryptoSlate
The proposal lists ETH returns to the Balancer DAO Multisig between Sept. 8 and Sept. 16 from the main greyhat, anonymous whitehats and block builder Ultrasound.money.
Reported by CryptoSlate
The 296.401711 ETH is the amount the proposal records as returned, not a promise of full reimbursement.
296.402 ETHReported by CryptoSlate
The proposal does not state a recovery percentage, and the attack loss is expressed in dollars at historical prices while the recovery pool is denominated in ETH.
Reported by CryptoSlate
No claim window is open, since the proposal still awaits a vote and publication of address-level claim data.
Reported by CryptoSlate
What happened
CryptoSlate reports that a Balancer V1 recovery proposal would divide 296.401711 ETH returned after an Aug. 31 exploit among liquidity providers in 120 legacy pools. The proposal records about $1.39 million in tokens drained from those pools at attack-time prices, and lists ETH returns to the Balancer DAO Multisig between Sept. 8 and Sept. 16 from the main greyhat, anonymous whitehats and block builder Ultrasound.money. Under the plan, each pool would first receive recovered ETH in proportion to its share of the total dollar loss at the time of the attack, and that pool's share would then be divided among providers by their pool-token holdings at Ethereum block 25,872,248, the block immediately before the first exploit transaction at block 25,872,249. CryptoSlate notes that the 296.401711 ETH is the amount the proposal records as returned rather than a promise of full reimbursement, that the loss is expressed in dollars at historical prices while the recovery pool is denominated in ETH, and that the proposal states no recovery percentage. No claim window is open, because the proposal still awaits a vote and the publication of address-level claim data.
How the story developed
- First report
First report by CryptoSlate
Why Balancer’s $1.4M hack recovery won’t pay LPs anytime soon
- Update
CryptoSlate reports on the Balancer V1 recovery proposal
The report describes a proposal to allocate recovered ETH across 120 legacy pools, with no claim window open.
- Update
Exploit drains tokens from Balancer V1 pools
The proposal dates the attack to Aug. 31 and puts the drained tokens at about $1.39 million at attack-time prices.
- Update
ETH returns reach the Balancer DAO Multisig
The proposal lists returns between Sept. 8 and Sept. 16 from the main greyhat, anonymous whitehats and block builder Ultrasound.money.
- Update
Proposal still awaits a vote and address-level claim data
Until both land, no claim window opens and no address-level figures are available.
Affected entities
Original sources
| Publisher | Report | Role | Published |
|---|---|---|---|
| CryptoSlate Crypto media | Why Balancer’s $1.4M hack recovery won’t pay LPs anytime soon | Original |