Liquid Federation restores LBTC 1:1 backing nine weeks after $320M exploit

The Liquid Federation announced on Monday, November 3, 2026 that reserves backing LBTC are back to 1:1 for the first time since the September 6, 2026 incident that let an attacker create roughly 4,000 unbacked LBTC and peg out about $320 million worth of BTC from the federation wallet. The restoration closed a lingering ~600 BTC gap left after the attacker's partial return of ~3,400 BTC the day after the hack. Blockstream has not disclosed who supplied the final transfers; Liquid Federation board member Samson Mow named Blockstream as the source. Primary sources: Liquid Federation announcement on X, Blockstream incident report. Coverage: The Block, Decrypt, CoinDesk.

What happened

On September 6, 2026, an attacker exploited a bug in cached range-proof verification in Elements, the full-node implementation that runs Liquid's federated sidechain. The bug let them mint roughly 4,000 LBTC with no corresponding BTC backing and then peg them out through SideSwap, a federation member authorised to co-sign peg-out transactions. According to Blockstream's incident report, the federation wallet reserve fell from about 4,205 BTC to 197 BTC in the aftermath.

The attacker — publicly describing themselves as white hats — returned about 3,400 BTC on September 7, keeping ~598 BTC. Blockstream, led by Adam Back, refused the attacker's demand for a 10% bug bounty on the retained coins; Back called the withholding "theft." The federation ran at a visible shortfall for nine weeks.

October 28: a 50 BTC deposit cut the gap to ~550 BTC outstanding (per Samson Mow on X). November 2: a 300 BTC transfer landed, followed by a 250 BTC transfer later the same day, closing the deficit. Mow attributed the top-up to Blockstream; Blockstream itself has not published a statement naming the source.

Blockstream's incident response produced Elements v23.3.4, released September 9, which disabled the vulnerable proof-validation cache and patched the affected bridge nodes. The patch is what let the attacker's refund path clear and what the federation ran on through the recovery.

Mechanism — the cached range-proof bug

LBTC is backed 1:1 by BTC held by a federation of functionaries (the Blockstream-led group of businesses that runs Liquid). Peg-ins deposit BTC and mint LBTC; peg-outs burn LBTC and release BTC. Elements validates confidential-transaction range proofs — the zero-knowledge argument that a value is non-negative — to prevent inflation of blinded amounts.

Elements caches validated proofs for performance. The September 6 bug was in that cache path: a crafted transaction let the attacker reuse an already-validated proof against a new, unrelated commitment, so the node accepted a mint of LBTC with no BTC behind it. The attacker produced roughly 4,000 fake LBTC and routed them through SideSwap's peg-out authorisation. Liquid's statement — that no keys were compromised and no network operators were hacked — is consistent with that read: the federation signed valid-looking peg-outs on top of an inflated supply, because the inflation itself was never detected.

The fix in v23.3.4 removes the vulnerable cache and reinforces proof validation. Elements v23.3.4+ is now required for federation nodes.

Numbers

• Exploit date: September 6, 2026
• Loss: ~4,000 BTC ≈ $320 million (at the time)
• Reserve before/after exploit: ~4,205 BTC → ~197 BTC
• Returned by attacker (Sept 7): ~3,400 BTC
• Withheld by attacker (ransom demanded, refused): ~598 BTC
• Patch: Elements v23.3.4, released Sept 9
• October 28 deposit: 50 BTC (gap reduced to ~550 BTC)
• November 2 deposits: 300 BTC + 250 BTC
• 1:1 LBTC backing restored: November 3, 2026
• Reserve deficit at restoration: 0.00 BTC (dashboard screenshot posted by Adam Back)
• Reserve dashboard: liquid.network

What to watch

1. Where the final ~600 BTC came from. The federation has not confirmed. Mow named Blockstream. A direct statement from Blockstream — treasury vs. new raise vs. insurance — would settle the open question for LBTC holders.
2. Peg-out restrictions. The federation imposed limits during the incident. Whether all restrictions lift at restoration, and the dated schedule, has not been published alongside the backing announcement.
3. Governance changes. The Liquid Federation said it is preparing revisions to governance and oversight "in the coming weeks." The specific proposals — functionary rotation, threshold changes, bug-bounty policy — matter more than the restoration itself.
4. Attacker attribution. No actor has been formally named. The withheld ~598 BTC sits on an identified address (not publicly listed in the Federation's November 3 statement); any further movement by it is on-chain and watchable.
5. Elements adoption. The post-mortem relied on fast upgrade of federation nodes to v23.3.4. Running nodes that are not federation functionaries — but which still speak the Liquid protocol — should be audited for cached-proof assumptions.

Context

The Liquid incident is the second federated-sidechain soundness failure of 2026 — the first being the Zcash Orchard NU6-2 emergency hardfork earlier this year, where a soundness bug in a shielded pool required a chain-wide forced upgrade. On Liquid, the geometry was different (a bug in validation caching, not in the proof system itself), but the economic shape was the same: a soundness break on a confidential-amount system is immediately exploitable at the full size of the pool, with no partial-leak gradient.

The event also validates the usual critique of federated-sidechain security: a federation can patch a soundness bug fast — Elements v23.3.4 landed three days after the exploit — but cannot easily refund a mint of fake backing without external capital. That the gap stayed open nine weeks is the operational truth, not the headline.

Finally, this is Liquid's most severe incident since launch in 2018. The federation's willingness to run at a disclosed shortfall rather than suspend peg-outs is a position that will be re-litigated the next time a federated sidechain hits a soundness bug; so will Blockstream's refusal to pay a 10% ransom to recover coins versus making LBTC holders wait on an undisclosed capital source. Both calls now have precedent.