Subscribe
Liquid's "white hats" gave back 3,400 BTC. Blockstream is negotiating for the other 600

Liquid's "white hats" gave back 3,400 BTC. Blockstream is negotiating for the other 600

A cache bug in Elements let someone mint unbacked L-BTC and peg out real bitcoin through SideSwap, with no key compromised and the sidechain still paused.

In briefExploit timing, mechanism, SideSwap peg-out, reserve 4,205 to 1971No keys compromised; peg-out as designed2Elements v23.3.4 and the recovery plan3
Updated · Sep 11, 2026, 02:51 ETThis story was revised after publication. The sources block reflects the current version.
A physical Bitcoin coin resting on a laptop keyboard
Photo: Satheesh Sankaran (CC BY 2.0)

Nobody stole a key. Which is the strangest part of the largest bitcoin loss of the year, and the part that should worry you if you settle real money on a federated sidechain.

On Saturday 6 September 2026 someone exploited a bug in the way Liquid nodes cache range-proof verifications, and created roughly 4,000 L-BTC that no bitcoin in reserve stood behind. Those tokens went to SideSwap, a federation member holding a peg-out authorisation key, which processed them like any other withdrawal. Twenty-three minutes later, by SideSwap's account, the federation had paid nearly four thousand real bitcoin to a customer address.

Liquid's reserve fell from about 4,205 BTC to 197.

The multisig was not broken. It was told a lie.

Liquid's incident report is careful, and correct, about the second half of that. "No keys were compromised. The Liquid Federation functionaries were not hacked ... The peg-out mechanism that authorizes withdrawals to whitelisted addresses operated as designed."

Eleven of the fifteen functionaries signed, which is exactly what the scheme was built to require. They were handed tokens that every node on the network considered valid, "because the validation failure occurred at the transaction level before the peg-out was initiated."

So this was not a theft in the ordinary sense. Compare it with the case we wrote up in The biggest crypto theft in US history went through a Google Drive, or with January's Step Finance loss, where attackers got at executives' devices and the keys those devices held. Here the chain simply believed something false about its own supply (and USDT and the other Liquid-issued assets were untouched).

The phrase "white hat" did not survive the weekend

Whoever did this described themselves that way in an on-chain message. "Please fix the bug first. The chain is under risk at latest commit right now. Make sure every node is patched. Then we will transfer the money back safely after confirming the fix."

By Monday 3,400 BTC had come back. About 598.5 BTC, worth roughly $47 million, had not. "Discussions between Blockstream and the individuals responsible are ongoing to secure the return of the remaining funds," Liquid said on Tuesday. On Wednesday Blockstream shipped Elements v23.3.4, reviewed by the Bitcoin Red Team, Alpen Labs and others, hardening the cache keys used for range proofs. It also told users to treat any "unsolicited 'white-hat' or bounty outreach" as a scam.

Ledger's chief technology officer, Charles Guillemet, stopped extending the benefit of the doubt once the 600 stayed out. "If this was ever a negotiated reward under an encrypted contract signed on-chain, it looks more like extortion than white-hat hacking!"

What do you call keeping 15 percent of $320 million? A bounty, set by the person taking it.

We would expect Blockstream to pay it, in the sense of accepting what came back as the recovery and quietly calling the rest a reward, because the alternative is restoring a network with a nine-figure hole in it while the federation's members are exchanges and brokers with customers of their own. That is probably the market price of a bug that lets somebody print bitcoin.

The structural problem outlasts the negotiation

Liquid's security model is that a federation of more than 80 firms cannot be corrupted member by member. Saturday showed the model has nothing whatever to say about a consensus bug, because every honest node validated the fake.

A federated peg seems to be only as sound as the least-reviewed line in its verification code. And Elements has far fewer eyes on it than Bitcoin Core does.

That is awkward for the pitch that Liquid is where bitcoin treasury companies and tokenised securities should settle. Five such products listed on Bitfinex Securities through Liquid in the first week of September, and their issuers have spent the days since explaining a paused chain to holders.

The sidechain is still down. Blockstream's plan is to resume block production with pegs suspended, replay valid transactions, and reopen pegs "once the network state has been fully restored including a return of funds." We would expect pegs to reopen before 30 September with the remaining coins still gone and the reserve made whole by Blockstream or by federation members.

If all of it comes back before the pegs reopen, the white hats were what they said they were, and we will owe them the label.

Sources

01
Exploit timing, mechanism, SideSwap peg-out, reserve 4,205 to 197“On September 6, 2026 at 15:53:10 UTC (Liquid block 4,050,336), a vulnerability in the open-source Elements software related to how Liquid nodes cache range proof verifications was exploited, resulting in the creation of ~4,000 LBTC that…” — x.com · primary · Sep 9
02
No keys compromised; peg-out as designed“Because the validation failure occurred at the transaction level before the peg-out was initiated, both SideSwap’s node and the Liquid Network’s globally distributed functionary nodes accepted the LBTC as valid. ... No keys were…” — x.com · primary · Sep 9
03
Elements v23.3.4 and the recovery plan“The emergency Elements v23.3.4 release is now available. ... This release addresses the proof-verification cache vulnerability, hardening the cache keys used for range proofs. Elements v23.3.4 has undergone multiple rounds of internal…” — x.com · primary · Sep 9
Show all 10 sources
04
Initial disclosure“Purported white-hat hackers have withdrawn ~4,000 BTC (~$320 million) from the Liquid Federation wallet. ... Other Liquid assets such as USDT, DePix, and RWAs are unaffected by this security incident. ... Effectively, the Liquid…” — x.com · primary · Sep 9
05
3,400 BTC returned; ~598.5 outstanding; talks ongoing“Blockstream is in talks to recover approximately 598.5 BTC still outstanding after the Liquid exploit. The individuals responsible returned 3,400 BTC on Monday, leaving roughly 15% unreturned. ... “Discussions between Blockstream and the…” — decrypt.co · reported · Sep 9
06
Guillemet's remark““The ‘white hats’ still hold 600 BTC,” Guillemet wrote on X. “If this was ever a negotiated reward under an encrypted contract signed on-chain, it looks more like extortion than white-hat hacking!”” — decrypt.co · reported · Sep 9
07
On-chain message; SideSwap's 23 minutes; federation structure““Please fix the bug first,” the on-chain message said. "The chain is under risk at latest commit right now. Make sure every node is patched. Then we will transfer the money back safely after confirming the fix.” ... the Liquid Federation…” — tomshardware.com · reported · Sep 9
08
Step Finance contrast“For example, in January, the Solana-based platform Step Finance lost roughly $40 million after attackers compromised devices belonging to its executive team, gaining access to the keys that guarded its treasury wallets.” — tomshardware.com · reported · Sep 9
09
Blockstream's scam warning“Treat as scams: "mandatory security update" emails and portals, refund / re-peg / "claim L-BTC" sites, fake support DMs, lookalike domains, and unsolicited "white-hat" or bounty outreach.” — x.com · primary · Sep 9
10
Five bitcoin treasury products listed via Liquid on Bitfinex Securities“Five bitcoin treasury company products have been newly listed on Bitfinex Securities. Tokenised securities of the world’s leading bitcoin treasury companies, and issued on @Liquid_BTC.” — x.com · primary · Sep 9
More on Bitcoin and Crypto crimeAll Bitcoin stories →
You’re 60% through. Stories like this one, Mon · Wed · Fri, with every claim sourced.