.jpg)
The attackers who drained roughly 3,996 BTC, about $320 million, from the Liquid Network are negotiating their own surrender, in public, on the Bitcoin blockchain itself. The on-chain conversation, confirmed in blocks 965,783 through 965,875, shows the intruders offering to return "most" of the stolen funds, provided Blockstream patches the vulnerability first. It is either the strangest white-hat story of the year or the most elaborate extortion, and the difference matters for every federated sidechain.
The mechanics first. The unauthorized withdrawal used a Peg-out Authorization Key associated with SideSwap, though Liquid says there is no evidence the key itself was compromised, a distinction that leaves the actual vector unexplained. The first peg-out confirmed in block 965,783 on Sept. 6, the same block carrying the attackers' OP_RETURN message: "we are whitehats. contact us on chain." Blockstream responded in block 965,822 with 1,000 satoshis and a message directing the attackers to its security team, signed with a detached PGP key verifiable against Blockstream's public key. In block 965,869, the attackers asked whether returning "most" of the BTC would be acceptable. In block 965,875, they demanded Blockstream "fix the bug first" and confirm every federation node has the patch before repayment. No return transfer has occurred.
"LIQUID WHITE HATS SAY THEY'LL RETURN 'MOST' OF 4000 BTC ONCE LIQUID NETWORK BUG IS PATCHED. The hackers have been conversing with Blockstream via OP_RETURN messages and PGP encrypted text." — Alex Thorn (@intangiblecoins), September 7, 2026
Liquid Network's insolvency problem, in one number
Ninety-five percent. That is the share of Liquid's reported Bitcoin backing reserves the withdrawal removed. L-BTC, the sidechain's synthetic bitcoin, is now functionally insolvent unless Blockstream or federation members backstop it, which is why the network disabled bridge nodes, requested exchanges halt L-BTC deposits and withdrawals, and effectively paused the sidechain. Other issued assets, stablecoins and real-world assets, were not directly taken. But a Bitcoin layer 2 whose defining promise is 1:1 federation custody just lost the 1:1, and 2026's exploit tally keeps mounting past $1.3 billion in protocol losses. Rain, Notional, and now Liquid have each demonstrated that the industry's custody architecture fails at the point everyone assumed was boring.
Now the skepticism, because "whitehats" is doing a lot of work in this story. Liquid calls them "purported white-hat hackers," which is institutional for "we do not believe you." The attackers set no timeline, no identity, and no definition of "most," and conditioning repayment on a patch is a neat framing: it converts a $320 million theft into an unpaid security audit with a bounty to be negotiated. If "most" means 90%, the attackers walk away with $32 million, a reward structure no bug bounty program on Earth would authorize. Every protocol with a federation wallet just learned that OP_RETURN ransom notes are now a category of incident response.
What this does to Bitcoin layer 2 confidence
The strategic damage outlasts the negotiation. Liquid was the flagship for federated Bitcoin sidechains, the architecture that promised Bitcoin-adjacent functionality without trusting a bridge. Draining 95% of reserves through what may be a process flaw rather than a key compromise indicts the federation model itself: multisig custodians are one governance failure away from exactly this, and no amount of "Bitcoin security" propaganda covers the gap. Watch two things: whether the promised return actually lands, and the technical postmortem, when it comes, explaining how PAK authorization was bypassed. If the funds return and the bug gets named, Liquid survives with a scar. If either stalls, the federation owes its users roughly $320 million it does not have, and Bitcoin's layer 2 story loses its flagship in a single weekend.
