On 6 September 2026 the Liquid Network, Blockstream’s federated Bitcoin sidechain, accepted transactions that created L-BTC nobody had locked. Independent analysis of Elements — the software Liquid runs — pointed at a range-proof verification cache: an expensive check whose cached “valid” result could be reused in a context where it did not apply. Unbacked L-BTC was then presented to SideSwap’s peg-out service. SideSwap said its Peg-out Authorization Key was not compromised; under the rules the functionaries were running, the paper looked like L-BTC. The federation wallet paid native bitcoin.
CertiK’s timeline puts a large peg-out on the order of 3,996 L-BTC, with native BTC landing on Bitcoin shortly after, and a much smaller earlier peg-out. Public figures clustered around four thousand BTC leaving a reserve that had been about 4,200. That is a sidechain vault emptying, not Bitcoin’s supply schedule changing. We will not write how to mint the paper. The product lesson does not need a recipe.
What happened
L-BTC is supposed to be bitcoin locked with Liquid’s functionaries, represented on a confidential sidechain. Peg-in locks BTC; peg-out burns L-BTC and releases BTC. Confidential amounts need range proofs so a hidden number is not secretly enormous. Caching those proofs is an engineering shortcut. A shortcut that does not bind the right context is how a clipboard prints IOUs. Blockstream’s public line, as reported, was that federation and peg-out keys were not stolen. SideSwap processed a customer peg-out. The bug was in what the nodes would accept as L-BTC.
Bridge nodes were disabled. The network paused. On 7 September, on-chain, about 3,400 BTC returned to the federation peg address. About 598.5 BTC remained out, in the figures circulating with the incident reports. Exploiters posted white-hat language; a return of most of the coins is a choice, not a protocol guarantee. An emergency Elements release is vendor homework. Treat “white hat” as a caption until the reserve and the pause are both boring again.
This is not the Ronin bridge (validator keys). It is not Wormhole (a signature check on another chain). It is not Cronos rolling back Tectonic. Liquid is a federation product sitting beside Bitcoin. Bitcoin mainnet kept producing blocks. Your bitcoin in a wallet you control did not become L-BTC and did not pay this bill.
Why it matters
Wrapped and pegged bitcoin is an IOU on someone else’s clipboard. A bridge is extra software, not a tunnel. An exchange balance is an IOU, not a wallet. Liquid’s clipboard is a sidechain with a peg wallet. When the software that decides “this L-BTC is real” is wrong, the vault can still pay, because paying is what the peg-out path is for. Confidentiality features are a product. They are also extra code.
If you held L-BTC, you held a claim on a federation plus a claim on Elements. If you held BTC on Bitcoin, this incident is someone else’s custody failure and a reminder not to treat a ticker that says “BTC” as one asset. Hardware wallets are a practice if you ever sign a peg-out; they do not save you from confirming paper. Phishing will now impersonate Liquid, SideSwap, and Blockstream “refund” pages. Nobody legitimate needs your recovery phrase to “re-peg”.
What happens next
A patch, a long pause or a careful restart, arguments about the 598.5 BTC still out, and a wave of lookalike domains. Watch Blockstream and Liquid status notices, not a stranger’s QR code. We will not turn a sidechain bug into a bitcoin price thesis, and we will not pretend main-chain Bitcoin printed coins.
Not a review of Liquid, Blockstream, or SideSwap. Not an instruction to peg in, peg out, buy, or sell bitcoin.
