Skip to content
Signal21

Newsletter

Never miss a signal

Get every new signal the moment it lands: the three-horizon Bitcoin read and company coverage, straight to your inbox. One email per update, no noise. Unsubscribe anytime.

One step left

Now confirm it from your inbox

We sent a confirmation email to your address. Click the button inside it and you’re in, without that click, nothing is subscribed.

Not seeing it? Check your spam folder: early deliveries sometimes land there. Marking it “not spam” makes sure you get the signals.

Bitcoin

Bitcoin outlook, 2026-09-10

A sidechain reservoir breaches before most of the value arcs back through Bitcoin.

Liquid drained of 4,000 BTC: the biggest hack of 2026 is being negotiated in Bitcoin transactions

Signal21 Editorial Desk

On Saturday, September 6, the federation wallet behind Liquid, the Bitcoin sidechain operated by Blockstream, paid out about 4,000 BTC to a single withdrawal. At the day's prices that was roughly $320 million, and it amounted to close to 95 percent of the bitcoin the sidechain held in reserve. Nobody stole a key. According to the incident report Liquid published on September 8, a vulnerability in Elements, the open-source software that runs Liquid nodes, sat in the way nodes cache the verification of range proofs. Someone used it to create about 4,000 L-BTC that no bitcoin backed, then pegged those tokens out for real bitcoin through SideSwap, an authorized peg-out service. SideSwap says its own systems were not compromised, and Blockstream's status page says the peg-out authorization key used for the withdrawal was not compromised either. The chain was paused within hours; Blockstream reports its bridge nodes were patched by 01:09 UTC on September 7.

What happened next is the part that makes this story unusual, and it is why we have added a live thread of it to our front page. At 18:30 UTC on September 6, the address holding the coins spent a small transaction carrying a text message in an OP_RETURN output: "we are whitehats. contact us on chain". An hour later a Blockstream address answered on the chain too, pointing to its security email. From then on the negotiation ran in public, one transaction at a time. Some messages were plain text, some were signed with Blockstream's published PGP key, and many were encrypted so that only the two parties could read them. Early on September 7 the coin holder wrote that most of the funds would be sent back to the federation's peg wallet, and asked whether that was acceptable; a PGP-signed reply said yes. The holder then insisted that the bug be fixed and every node patched before any transfer. At 09:41 UTC a signed Blockstream message confirmed the bridge nodes were patched and the funds were safe to return, and at 16:09 UTC a single transaction sent 3,400 BTC back to the peg wallet. The remaining 598.5 BTC, about $47 million at the time, stayed put.

That balance is where the story stands tonight, and it has turned sour. After a sad-face message on September 7 and a note on September 8 that all further messages would be in plaintext, the holder posted on September 9 an ultimatum accusing Blockstream of spending too little on security and demanding that the company pay 10 percent from its own money as a bug bounty, or else expose its users to a 15 percent loss. Blockstream has kept answering in encrypted, signed messages, the latest early on September 10, and has not publicly accepted that framing. Ledger's chief technology officer said the arrangement looked more like extortion than white-hat work, and Signal21 has no way to judge the group's intent, so we call them the exploiter and record that the white-hat label is their own. The rest of the recovery is visible in the open: the Elements maintainers published a patched release on September 9, and on September 10 Blockstream's status page said Liquid had resumed producing blocks without user transactions as a precaution, with peg-ins and peg-outs still suspended. Adam Back, Blockstream's chief executive, was reported saying the one-to-one L-BTC peg will be covered. Who pays for the shortfall, and how, has not been spelled out.

For Bitcoin holders, three things are worth separating. First, nothing in this incident touched Bitcoin itself: the bug lives in a sidechain's software, the theft was of bitcoin held by a federation, and the base layer processed the drain, the messages and the return exactly as it processes everything else. Second, it is a reminder that a federated sidechain is a custody arrangement with extra steps, and that "not your keys" applies to L-BTC as much as to an exchange balance. Third, the market shrugged. Bitcoin closed September 6 near $80,339 and drifted to about $77,275 late on September 10, with a low of $76,630 today. That keeps the price above the $75,600 line our recent notes have set as the bears' burden, and below the $81,000 to $84,000 band that capped May and marks January's breakdown level. Our three horizon views are unchanged, refreshed today with the same views on all three horizons; the next dated catalyst on our calendar remains the Senate's September 15 vote on the CLARITY Act.

We show the attributed thread between the exploiter and Blockstream on our front page, updated as blocks confirm, with each line linked to the block that carries it. Encrypted messages are shown as encrypted; we do not decrypt them and cannot. The chain will record how this ends.

This is general market commentary, not investment advice or a recommendation to buy or sell any asset.

Sources

All Bitcoin articles