The largest bitcoin sidechain lost almost all of its bitcoin on Sunday afternoon, and it did so through the front door. At 14:05 UTC on September 6, 2026, someone submitted 4,000 L-BTC to the peg-out portal run by SideSwap, one of Liquid's approved exit points, per CryptoTicker's reconstruction. At 14:28 UTC the federation's 11-of-15 multisig did what it is built to do and released 3,996 BTC to an external bitcoin address, confirmed in block 965,783. Protos counted 83 inputs, each spent with exactly the 11 valid signatures the arrangement requires. That is roughly $320 million at Sunday's prices and, per The Block, about 95 percent of the approximately 4,200 BTC that backed every L-BTC in circulation. The reserve page at liquid.network showed 4,205 L-BTC outstanding against 197 BTC held by the time anyone noticed, under 5 percent backing for a token whose entire pitch is a 1:1 peg. Liquid posted on X that it was aware of a security incident, said the SideSwap peg-out authorization key had not been compromised and neither had any other key, disabled the bridge nodes so no new transactions could be submitted, and told exchanges to suspend L-BTC deposits and withdrawals. In Blockstream's own words on its status page, the Liquid sidechain is effectively paused until the issue is resolved.
The mechanism, as far as it has been described publicly, is worse than a stolen key. Blockstream attributed the L-BTC to a bug in Elements, the open-source codebase Liquid runs on, and SideSwap said the same, calling it faulty L-BTC originating from a third-party Elements bug. Independent analysis relayed by CryptoTicker points to a consensus-level flaw in how Elements cached confidential transaction rangeproofs: the cache key left out the asset and script context, so a proof that had been verified once could be reused where it should have failed, and unbacked L-BTC could be created and accepted by a subset of nodes. Per the same outlet, a fix had already been merged into the Elements repository but had not shipped in a tagged release. Protos could not confirm which commit was the exploited one and flagged a September 1 validation fix for dynafed headers as a candidate. Casa's Jameson Lopp, quoted by Protos, observed that the Liquid functionary codebase appears not to have been touched in two years, which he did not consider a good sign. The honest summary is that the federation signed a legitimate peg-out for coins that should never have existed, and every signer's software agreed they did.
Submitted through SideSwap, minted by an Elements bug.
11 of 15 federation signatures on 83 inputs.
Sidechain paused, exchanges asked to freeze L-BTC.
Whitehat claim, fix-first demand, PGP-signed reply.
Promise covers most of the coins, no deadline.
A ransom negotiation conducted in OP_RETURN
What makes this incident unusual is that the whole conversation is public. Shortly after the peg-out confirmed, the receiving address broadcast an OP_RETURN message reading "we are whitehats. contact us on chain." Blockstream answered at block 965,822 with security contact information, per CryptoTicker, and a second address offered a Signal handle, per Protos. At block 965,875 the taker set their terms, per The Block: fix the bug first, make sure every node is patched, and then the money comes back safely after the fix is confirmed. Blockstream then sent a PGP-signed on-chain message, verifiable against the security key on its website, reading "Bridge nodes are patched, safe to return the funds." As of Monday morning nothing had moved: Protos put the balance in the taker's address at 3,998 BTC, and Bitcoin.com noted that the taker's later wording promised to return "most" of the funds rather than all of them, with no deadline attached. An unsigned on-chain message offering a 98 BTC bounty also appeared, per Bitcoin.com, which may have come from an impersonator. Bitcoin.com also pointed out that Blockstream CEO Adam Back had not posted about the matter personally, which left the status page and the on-chain messages as the company's only public statements a full day after the drain.
We would treat the white hat label as a claim rather than a fact until the coins are back. Real white hats generally do not take 95 percent of a reserve to prove a point, and "most" is a word that leaves room for a very large finder's fee. The frame that matters more is what Liquid is used for: per The Block, it is a settlement layer for exchanges and financial firms, Blockstream lists Bitfinex and BTSE among its users, and L-BTC is the collateral for a good deal of confidential over-the-counter flow. Every one of those holders now owns a claim on a reserve that is under 5 percent funded, pending a stranger's goodwill. Other assets on the sidechain, including USDT, DePix and tokenized real-world assets, were not affected by the bug, per Blockstream's status page, but they are frozen with everything else until the network restarts, and no restart timeline has been published. Bitcoin's base layer was untouched, which is the one line of the story that does not need a caveat. This is the second nine-figure bitcoin security failure in a month after the Coldcard entropy exploit, and the lesson is the same one our security basics guide keeps repeating: any layer between you and the base chain, whether a wrapped token, a bridge or a federation, is a counterparty, and counterparties fail.
The market barely flinched, for now
The drain landed on a market that was already leaning cautious, and the price reaction was small. Bitcoin opened Monday at $80,351, 0.7 percent above Sunday's open, then slipped to $79,350 by 9:41 a.m. ET, per Yahoo Finance, which framed the week as a rate watch ahead of the August CPI and PPI prints that Fed officials have named as the deciding inputs for the September 15 to 16 meeting. CoinDesk's Monday read had bitcoin down 1.3 percent since midnight UTC while the weekend's altcoin push faded: Bittensor, Kaspa, Internet Computer and Celestia had each gained more than 12 percent over 24 hours, most of it before midnight, and were handing part of it back. Positioning is the more telling number. Futures open interest fell to 670,000 BTC from 709,000 on Friday, the lowest since March 23, per CoinDesk, and the taker buy-sell ratio leaned short at 51.6 percent, a reversal from Friday's bullish reading. Leverage was already leaving before the Liquid headline, which is one reason a $320 million hole in a sidechain did not produce a cascade: the coins did not hit the market, and the traders most likely to panic had largely deleveraged into Friday's jobs shock.
Two things would change that. The first is the 3,998 BTC moving anywhere other than back to the federation; a sale of that size into a thinning order book would be felt, and a partial return would tell the market what the finder's fee was. The second is the post-mortem, because the answer to whether other Elements-based deployments shared the same cache bug decides whether this was a Liquid problem or a class of problem. Per The Crypto Times' tally, the first week of September has now logged $322 million in reported exploits, and one incident is 99 percent of it. We will update this page when the coins move, when Blockstream publishes its technical account, or when the sidechain restarts, whichever comes first. Nothing here is trading advice, and if you hold L-BTC on an exchange the only useful action today is to read that exchange's own notice rather than anyone's thread.
