The day 95% of Liquid's reserve walked out — where 'wrapped' bitcoin risk actually lives

At 10:00 UTC on September 10, the Liquid Network stepped back onto the tape. Block production had resumed — as a precaution. Transactions remained paused. And the peg-outs that are the entire reason anyone locks bitcoin into the network were still switched off.

That is the record four days after roughly 4,000 bitcoin, worth about $320 million at the time, walked out of the federation wallet that backs Liquid's token. This is a record, not a call. Here is the tape, then the mechanism, then the question the incident leaves hanging over every "wrapped" bitcoin an investor can hold.

The tape

On September 6, Blockstream, the company that operates Liquid, disclosed the withdrawal: nearly all of the ~4,200 bitcoin held in the federation's reserve had been drained, leaving roughly 200. At the time that was about 95 percent of what stood behind L-BTC, the network's one-for-one bitcoin substitute. The halt was immediate — bridge nodes disabled, and exchanges paused L-BTC deposits and withdrawals.

The money did not come back all at once, and it has not fully come back. The actors, who called themselves white-hat hackers, returned 3,400 bitcoin — about 85 percent of what they took — once Blockstream said the nodes were patched. About 598 bitcoin, worth roughly $46 million, still sat in a withdrawal-linked address as of reporting, and no public agreement described it as an approved bounty.

That is the tape. The reader's real question — how 95 percent of a network's backing could leave without anyone's private key being stolen — has an answer, and it is not a headline.

The mechanism: the bridge broke, not Bitcoin

No signing key was taken. The federation's 11-of-15 multisig wallet was not compromised, and neither was the Peg-out Authorization Key that SideSwap, a Liquid wallet service, uses to release bitcoin. The failure was narrower and more interesting: a bug in Elements, the open-source software that runs Liquid, in the way it cached cryptographic proof checks.

In plain terms, the software cached the result of a successful verification to save work, then failed to check that the cached result belonged to the transaction it was being asked to approve. The attacker submitted real data, got it verified, then pointed a second, different transaction at that cached approval. Nodes accepted invalid data as already validated. Liquid minted L-BTC that was not backed by locked bitcoin — "minted out of nowhere," in Blockstream's own phrasing — and those tokens were burned through a legitimate peg-out path to release real bitcoin to the attacker.

This is the detail that matters, and it generalizes past Liquid. L-BTC is not bitcoin; it is a promise that a federation wallet and a piece of validation software will honor a redemption. When L-BTC is fully backed, the promise is as good as the 15 authorized signers and the code they run. When that code fails, the redemption path can collapse even though the underlying bitcoin never moved and its chain never even blinked.

The base chain did not blink. Bitcoin traded around $77,000 on the day, down roughly two percent — a normal move, inside a 52-week range that has stretched from about $58,000 to $125,500. No liquidation cascade, no peg-wide repricing. The market decided this was a bridge event, not a Bitcoin event. That containment is the most useful thing about the episode: the strike landed on the layer that exists to move value, and the asset itself absorbed it.

The ritual, read as a ritual

The "white-hat" label deserves the same treatment the tape gives every claim: record it, then ask what it actually buys. White-hat practice normally means finding a flaw with permission and a pre-agreed scope, not moving $320 million out of a live system and naming your own bounty afterward. The controls were never tested by consent; they were broken. Ledger's CTO put it bluntly, arguing that holding roughly 600 bitcoin without publicly disclosed terms looks less like a security reward than like extortion. The claim that the keepers are heroes is asserted, not documented, and a ritual that implies a financial return is exactly the kind whose reach should be discounted until terms are on the record.

What this costs the company's thesis

There is no Blockstream ticker to buy — the company is private — so the investment read-through is indirect. But the economics are worth naming. In October 2024 Blockstream closed a $210 million convertible-note round led by Fulgur Ventures to build out what it calls "financial infrastructure technology powered by Bitcoin." Liquid is the flagship of that story: a layer-2 where institutions and applications can hold a bitcoin substitute, issue assets, and move money confidentially. The whole product is a redemption path. That product just proved it can be paused by a software bug while its reserves were briefly down to five percent.

Bloomberg framed the incident as another dent to crypto's effort to convince banks and institutions that digital assets belong in mainstream financial plumbing. That is the right container to watch. Institutions do not underwrite "wrapped" assets because they trust the base chain; they underwrite redemption certainty — that a token can actually be turned back into the coin it claims to be. This episode is a demonstration of redemption risk at scale, settled in four days but not yet closed. A $320 million drain is a stress test the industry passed only because the takers gave most of it back.

Until block production runs with transactions again, the peg is not fully restored, and the remaining ~598 bitcoin is either an agreed reward or still out the door. One open print, and it decides which story the record tells: a controlled white-hat exercise, or a jailbreak the network bought back. That is the falsifier for the ritual. The falsifier for the map — whether institutions actually retreat from sidechain and bridge infrastructure — is quieter, and it will show up in the flows and launches over the coming months, not in the status page.