Liquid lost 95% of its Bitcoin reserve with "every key intact" — the one place a 1:1 peg can break

At 14:28:56 UTC on Sunday, September 6, an 11-of-15 multisig signed a transaction releasing 3,996.02 Bitcoin — about $320 million — from the federation wallet that backs Liquid Network's L-BTC token. Nothing about that signature was forged. Every key was real and untouched. The payment went to a fresh Bitcoin address whose owners, hours later, left a message on the main chain: "we are whitehats. contact us on chain."

That detail is why this week's biggest crypto story is a record rather than a fumble. A network marketed as boring, bank-grade settlement infrastructure drained roughly 95% of its Bitcoin reserve through its normal exit door — because of a bug in the software that checks whether a token exists, not because anyone stole the keys. Here is the tape, and what it says about a promise most retail holders assume to be ironclad.

What Liquid is, and what broke

Liquid is a federated sidechain run by Blockstream and 15 rotating "functionary" organizations. Exchanges and stablecoin issuers use it as a fast, cheap settlement layer — moving L-BTC between one another instead of settling every trade on Bitcoin's base chain. The whole design rests on a single promise: every L-BTC in circulation is backed 1:1 by real Bitcoin held in a federation wallet and redeemable through a "peg-out."

The exploit never touched that wallet's keys. The vulnerability sat in Elements, the open-source software Liquid runs on — specifically in how it caches "range proofs," the cryptographic checks that confirm confidential-transaction amounts are valid and weren't conjured from nothing. An attacker fed the network data that reused an old cached verification result, so nodes accepted roughly 4,000 L-BTC that had no Bitcoin behind them as valid. At 14:06:10 UTC, a peg-out request moved those phantom tokens through SideSwap, a federation member authorized to process withdrawals, and the 11-of-15 quorum — which only sees that the software says the transaction is valid — released the real Bitcoin. The reserve fell from about 4,205 BTC to about 197 BTC in under an hour.

That is the uncomfortable part. In a multi-signature system, controlling the keys is supposed to be the perimeter, and the perimeter held. The failure happened one level earlier, in the validation that decides what the keys are agreeing to. Two explorers even disagreed afterward about how much L-BTC existed, because the minted-but-unbacked coins were invisible inside confidential transactions. The "1:1" number you are told is a check on math; this week it turned out to be a check on code.

The return, read as a ritual

Then came the collectible moment. The actors called themselves white hats, saying on-chain they would return the money once the vulnerability was patched on every node. Blockstream deployed Elements v23.3.4 to its bridge nodes; the group sent back 3,400 BTC — about 85%, worth roughly $270 million at the time — the next day. Roughly 598.5 BTC, about $47 million, stayed in the withdrawal address, framed as an apparent bounty, with no public terms for keeping it.

Read that return as a negotiation, not a gift. It was conditional on the fix. The remainder has not moved. And Ledger's chief technology officer publicly rejected the white-hat label, calling the retention of about 600 BTC without disclosed terms closer to extortion. "White hat" is a claim with a date on it, not a verified fact; the polite reading is that the network bought back most of its reserve by patching on demand.

Where the peg lands

On Thursday, September 10, functionary nodes resumed signing and validating blocks — but "without transactions". Regular transfers and every peg operation remain suspended, and no date has been given for restoring them. Anyone holding L-BTC cannot currently redeem it for Bitcoin; the bridge that a layer of exchanges and stablecoins sits on is switched off at the point where peg-out approvals live.

Bitcoin itself barely reacted — down about a percent around the news and trading back, a market verdict that the problem was isolated to the sidechain, not the base layer. That is the easy and largely fair read. The harder one is decided by two prints, each falsifying one side of the story. The first is the outstanding 598.5 BTC: returned under disclosed terms, or left to sit as the tacit price of doing business. The second is the recovery choice itself — Liquid's stated plan to restore 1:1 backing turns on nullifying the invalid peg-out, which is really a decision about who absorbs the residual hole in the reserve.

For a retail investor there is no stock here to buy or short. There is a category of claim to re-examine. "Backed by Bitcoin" is a promise enforced by code, and code can disagree with reality and still be signed in good faith by eleven organizations that trusted it. Anywhere a stablecoin or a wrapped token leans on a federation's word for its "1:1," the question this week's tape raises is now the first one worth asking: whose software is counting the reserve, and what exactly happens to the promise the day it is wrong?