Liquid Network Hack: $320 Million In Bitcoin Walked Out, And The Hacker Wants To Give It Back

Bitcoin's oldest sidechain just lost almost everything it was holding, and the person who took it is asking politely how to give it back.

On Saturday, 6 September 2026, roughly 4,000 $BTC worth about $320 million left the federation wallet that backs Liquid Network, the Blockstream-built Bitcoin sidechain that has been running since 2018. The wallet held around 4,200 BTC before the incident. It now holds a little over 200. That is about 95% of every Bitcoin ever pegged into Liquid, gone in the space of 23 minutes.

Then things got strange. The attacker attached a message to a Bitcoin transaction announcing himself as a white hat and inviting Blockstream to get in touch. Blockstream did. The two sides have spent the weekend negotiating a $320 million return in public, one small Bitcoin transaction at a time.

What Actually Happened In The Liquid Network Hack?

The timeline is unusually clean, because most of it is on the Bitcoin blockchain.

At 14:05 UTC on 6 September, a customer sent 4,000 L-BTC to SideSwap's peg-out service. SideSwap is a Liquid Federation member and a normal, approved route for converting L-BTC back into real Bitcoin. It processed the order like any other: the L-BTC was burned on Liquid, a valid peg-out authorisation was attached, and 23 minutes later the federation paid out roughly 3,996 BTC on the Bitcoin mainchain.

Nothing about that transaction looked wrong. It was confirmed in Bitcoin block 965,783 at 14:28:56 UTC, and the coins landed in a single address holding just under 4,000 BTC.

Shortly afterwards, that same address broadcast a tiny second transaction carrying an OP_RETURN message: the sender identified himself as a white hat and asked to be contacted on-chain. Blockstream replied the same way, sending 1,000 satoshis to the address in block 965,822 with a message pointing to its security contact. The conversation has since moved into PGP-signed notes passed back and forth.

Liquid disabled its bridge nodes and paused the network. Exchanges were notified, and several have suspended L-BTC deposits and withdrawals.

How Did The Elements Bug Let 4,000 BTC Out?

This is the part that should worry people more than the missing money.

Liquid's security model looks solid on paper. The Bitcoin backing L-BTC sits in an 11-of-15 multisig controlled by vetted federation members, and peg-outs back to Bitcoin are gated by a second layer called Peg-out Authorisation Keys. Neither of those layers broke. No key was stolen, no signer was phished, no hardware security module was tricked.

Instead, Blockstream has attributed the incident to a software bug in Elements, the open-source codebase Liquid runs on. Independent analysis points to a consensus-level inflation bug in how confidential transaction rangeproofs were cached. A cache key that left out asset and script context meant a previously verified proof could be reused, which let unbacked L-BTC be created out of nothing and accepted by a subset of nodes.

From there the attacker did not need to hack anything else. He simply redeemed his counterfeit L-BTC through the front door. SideSwap has said it had no way to tell the exploit-created coins apart from real ones, so it treated them the same, and the federation's HSMs signed a withdrawal that was perfectly valid under Liquid's consensus rules at the time.

The uncomfortable footnote: a fix had reportedly already been merged into the Elements repository days earlier, but had not yet shipped in a tagged release.

Is The Liquid Network Hacker Really A White Hat?

He says he will return most of the funds once the bug is patched and every node has updated. He has not said how much "most" means, has not given a deadline, and has not revealed who he is. As of Monday, the Bitcoin has not moved.

Plenty of people in the industry are not buying the framing. Ledger CTO Charles Guillemet pointed out that genuine white hats disclose a flaw before moving hundreds of millions in collateral, not after, and compared the situation to the Ronin bridge hack and the Euler Finance attacker's post-exploit change of heart. Draining a bridge and then asking for a chat looks less like responsible disclosure and more like leverage.

Former Blockstream CSO Samson Mow added another wrinkle, saying a Signal contact request that surfaced during the negotiation did not come from the address actually holding the coins. Which is a good reminder that in a public negotiation with an anonymous counterparty, anyone can pretend to be either side.

What Does This Mean For Bitcoin And L-BTC Holders?

Bitcoin itself is fine. The exploit never touched the base layer, and BTC has been sitting comfortably near $80,000 through the whole episode. This was a bug in a system built on top of Bitcoin, not in Bitcoin.

The damage is concentrated where you would expect: L-BTC liquidity, and any business or token that depends on Liquid as a settlement layer. Liquid exists to give exchanges fast settlement by issuing L-BTC against locked Bitcoin, and a reserve that is 95% empty is not a functioning peg. Until the coins come back, or the federation explains how it will cover the hole, L-BTC redemptions are stuck.

There is also a broader point about federated bridges. Liquid's federation did nothing wrong in the sense that everyone followed the rules. The rules themselves were wrong for a few blocks, and that was enough. For anyone holding assets through a bridge, custodian, or wrapper, a protocol-level bug in a shared reserve is a risk no amount of personal opsec can audit away.

What Happens Next?

Three things to watch:

• A confirmed return transaction. Nothing else counts. Until Bitcoin moves from that address back to the federation, the promise is just text in an OP_RETURN field.
• Blockstream's post-mortem. The company has not yet published a full technical account, including exactly how the peg-out cleared normal controls and why the Elements fix had not shipped.
• Reconciliation. Even in the best case, someone has to explain the gap between 4,000 BTC and "most" of 4,000 BTC, whether any of it is being kept as a self-awarded bounty, and how the remaining reserves are accounted for.

This story is not over when the hacker says nice things. It is over when the Bitcoin is back and the numbers add up.