The party that pulled 4,000 bitcoin out of the Liquid Network federation wallet has sent back 3,400 of them, 85% of the haul, after demanding that Blockstream patch the flaw first. They kept 598.5 bitcoin, worth $47.3 million. The entire negotiation played out in public, through messages written into Bitcoin blocks and signed cryptographically. The network is still halted.
Key Takeaways
- 3,400 bitcoin returned out of 4,000 withdrawn, 598.5 retained at $47.3M
- The party demanded a patch before returning funds, Blockstream answered with a PGP-signed message
- Root cause was an Elements software bug, no authorization key was compromised
Get an AI Summary of This Article
ChatGPT3,400 Coins Back, 598 Still Out
On Sunday, roughly 4,000 bitcoin left the Liquid Network federation wallet, close to $320 million at the time. By Monday, 3,400 of them were back. The episode closed inside forty-eight hours.
The rest is still outside. The party held onto 598.5 bitcoin, worth $47.3 million, roughly 15% of what they took, and no explanation accompanied the split. Nothing in their messages signals what they intend to do with the remainder, nor whether the share was chosen as a fee or simply kept. The opening chapter, when Blockstream watched 4,000 bitcoin walk out of its sidechain, pointed to a far harsher ending than this one.
The negotiation itself is the part worth recording. Both sides communicated through OP_RETURN messages written directly into Bitcoin blocks, layered with PGP encryption. At block 965,875, the party set the condition plainly: fix the bug first, and confirm every node had taken the patch.
Blockstream replied with a cryptographically signed message confirming the bridge nodes were secured. The 3,400 bitcoin moved at block 965,950, seventy-five blocks later. The company led by Adam Back treated the exchange as a public technical procedure, verifiable by anyone watching the chain, rather than a private settlement whose terms nobody could audit.
That format matters more than it looks. A signed on-chain exchange leaves a permanent record of who committed to what and when, which removes the usual ambiguity about whether a recovery was negotiated, coerced or simply invented after the fact.
The sequencing also tells you something about leverage. The party held the funds and set the terms, and the operator had to demonstrate a fix before anything came back. In practice the code review ran on a clock set by whoever was holding the money, which is an uncomfortable position for any operator to sit in.
Seventy-five blocks separate the demand from the transfer, and the whole episode resolved inside forty-eight hours. That window had to cover the patch, its propagation to bridge nodes, and the verification the party asked for. It is a fast turnaround for a codebase-level defect, and speed here cuts both ways: it recovered the funds, and it compressed the time available to scrutinise the fix.
An Elements Bug, Not a Compromised Key
The technical root cause reframes the whole incident. The unauthorized bitcoin creation came from a bug in the Elements software, the codebase Liquid runs on. No authorization key was stolen, and SideSwap systems were not compromised.
That distinction separates a key theft from a design defect. In the first case you revoke access and move on. In the second you audit the code, ship a patch, then convince every operator the fix genuinely holds before anything restarts.
It also changes who carries the residual risk. A stolen key is a failure of custody procedure, contained to whoever held it. A defect in the issuance logic touches every unit the chain has produced, because the question stops being who got in and becomes whether the supply on display was ever real. That is a far harder claim to close out publicly, and it is the one Liquid now has to settle.
The Liquid Network responded by halting operations outright, disabling its bridge nodes and freezing L-BTC deposits and withdrawals at exchanges. The reflex mirrors early September, when Crypto.com cut its own blockchain after a $75M theft rather than let a network run in a state nobody could vouch for.
Bitcoin infrastructure flaws have run through the whole summer. In August, a BTCPay Server flaw drained Lightning nodes, a different mechanism with the same root: widely deployed code, thinly audited, carrying real money.
What links these incidents is exposure rather than attacker sophistication. A codebase securing hundreds of millions of dollars does not automatically attract an audit budget proportional to what it holds, and the gap gets settled in a single afternoon.
The pattern repeated across DeFi too, most visibly with three protocols drained of $35M inside six hours. In none of those cases did a patch arrive before the money did.
Halting the chain is the honest response to that class of failure, and it is also the expensive one. Freezing L-BTC deposits and withdrawals at exchanges cuts the token off from its liquidity venues for as long as the review runs, which turns a software defect into a market access problem for everyone holding it.
The alternative was worse. Letting the network run while the supply of L-BTC could no longer be trusted would have pushed the loss onto whoever traded the token in the meantime, and the reputational bill for that lands on the operator either way.
Also on Cryptonomic:
- Bitcoin Drops Under $79K Two Days Before US Inflation
- Bitcoin Sees Quantum Closing In Faster Than Expected
- Blockstream Loses 4,000 Bitcoin From Its Liquid Sidechain
What the Federation Has to Prove Before Restarting
In the near term, the question facing L-BTC holders is blunt: is the token still backed one for one? With 598.5 bitcoin missing from a federation wallet, the answer depends on who absorbs the hole. Blockstream has said nothing on that point.
Voluntary returns remain the exception in incidents of this size, and they reveal nothing reliable about motive. When the funds stay gone, only the legal route is left, which is slow, expensive and far from certain to deliver.
Some victims take that route anyway, as Bybit did by suing North Korea over $1.5B. Here the party handed back the bulk before any proceeding could begin, which spares the federation a multi-year fight it would probably not have won.
Over three to six months, the real subject is the security model of Bitcoin sidechains. The Liquid Network rests on a federation of operators, an accepted trade between functional flexibility and the guarantees of the base chain. A software bug alone conjured bitcoin that never existed, and no amount of signer decentralization would have stopped it.
That is the objection any Bitcoin-anchored protocol courting institutional deposits now has to answer directly. A voluntary return closes this specific episode without closing the argument, because the next custodian conversation will start from the bug, not from the outcome.
There is a second-order effect worth watching on the sidechain question more broadly. Every layer built on top of Bitcoin trades some of the base chain’s guarantees for functionality it cannot get at layer one, and each incident of this type reprices that trade for the whole category rather than for one network.
For holders, the practical checklist has not changed and it is short. Know which entity actually holds the backing, know what happens to the peg when part of it goes missing, and know who publishes the answer. Liquid has yet to answer the second question, and until it does, the restart date matters less than the disclosure that comes with it.
Follow the story on Cryptonomic.
