Morning Edition · Thursday, September 24, 2026Published at 1:46 AM EDT · New York
Nearly 4,000 unbacked Liquid bitcoin were minted and 3,996 bitcoin were withdrawn in a single block. About 598 bitcoin remain with an attacker who calls himself a security researcher.

Blockstream has published its security incident assessment of the September 6 attack on Liquid, the bitcoin sidechain it operates for exchanges and trading firms. The report, along with independent analyses collected by Rekt News, points to the same failure. Liquid nodes cache the result of verifying range proofs, the cryptographic checks that confirm confidential transaction amounts are valid without revealing them, and that cached result was reused in a context it did not actually cover.
The consequence was an unbacked mint. The attacker created close to 4,000 Liquid bitcoin without depositing any collateral and withdrew 3,996 bitcoin through the peg, cutting operating reserves from 4,205 bitcoin to 197. Blockstream patched the bridge nodes within hours, block production stopped for roughly four days, and the network resumed on September 10. Roughly 3,400 bitcoin came back almost immediately. The remaining 598.5 bitcoin have not, and the person holding them has asked for a ten percent payment in exchange for returning them. Blockstream has said it will not pay to recover stolen funds.
The defect was not in application code. It sat in an optimization inside Elements, the open-source node software Liquid inherits from Bitcoin Core, so audits aimed at contract logic never covered the place the funds actually left the system. The same pattern has surfaced this year in oracle forwarders and validator signature sets: the component did exactly what it was written to do, and the specification behind it was wrong.
Liquid also demonstrated the trade-off built into its design. A federation of functionaries holds the peg keys and can coordinate a halt, which is how 3,400 bitcoin were stopped and how a patch reached every bridge node in under ten hours. A permissionless chain has no such option. Users who chose Liquid for fast settlement accepted that a small, identifiable group controls both the failure and the remedy.
Blockstream's federation model gains a demonstration that a known group can halt a chain and recover most of the funds, and competing sidechain and rollup designs gain a case study arguing that federated pegs concentrate both the failure and the remedy.
Part of a tracked trend
Unaudited Open-Source Crypto Code Surfaces at Scale
Coordinated volunteer and AI-assisted review keeps exposing large backlogs of undiscovered defects in the open-source libraries that wallets, nodes and protocols depend on, so disclosure waves — not novel attacker research — become a recurring driver of emergency patches and incident risk across the ecosystem.
Start a discussion in Townsquare.
More from this edition
Independent analysis by the security firm SlowMist matches Blockstream's account of a range-proof cache collision in Elements, but the totals differ between reports (3,998.5 minted, valued anywhere from $316 million to $400 million), and the attacker's self-description as a security researcher and the reported ten percent demand rest on Blockstream's telling alone, per SlowMist's published breakdown.
An open-source-intelligence read of how likely this story is true with its real nuance, not a judgment of any outlet. It assesses the claim, weighing independent and adversarial reporting. How we label confidence.
What this means
Exchanges and market makers holding Liquid bitcoin carry the residual loss through the peg, because reserves briefly fell to 197 bitcoin against nearly 4,000 in circulating claims, and the backing was restored only through a voluntary return and a coordinated halt. The wider exposure reaches every chain running Elements-derived code, and it tests Blockstream's institutional sales case, which rests on the argument that a known federation is safer than an anonymous validator set.
What to watch
Observations to monitor, not financial advice.
Synthesized from: Blockstream Blog · Rekt News
Comments
0No comments yet.