1 hour ago
14
Nearly $320 million in Bitcoin walked out of the Liquid Network’s federation wallet on September 6, and nobody has gotten it back yet.
The incident saw 3,996 BTC pegged out from the Bitcoin sidechain operated by Blockstream after a corresponding burn of Liquid Bitcoin (L-BTC). The federation’s reserves, which held roughly 4,200 BTC before the event, dropped to approximately 197 BTC. That’s a 95% decline in a single transaction processed around 14:28 UTC.
What actually happened
The sequence started when SideSwap, a decentralized exchange built on Liquid, facilitated a customer submission of 4,000 L-BTC at 14:05 UTC. Twenty-three minutes later, 3,996.01834922 BTC left the federation’s multisig reserves on the Bitcoin mainnet through what’s known as a Peg-out Authorization Key, or PAK.
Both Blockstream and SideSwap attributed the withdrawal to a bug in the Elements node software, the open-source codebase that powers Liquid’s infrastructure. Not a compromised key. Not an external hack. A software flaw that allowed the peg-out to process in a way it shouldn’t have.
Liquid operates on an 11-of-15 federation model, meaning 11 of 15 designated entities must sign off on peg-outs. The bug apparently circumvented the intended safeguards of that system.
The federation moved quickly after the withdrawal, pausing all bridge nodes and alerting exchanges to halt L-BTC deposits and withdrawals. That firewall prevented further drainage, but it also froze the bridge that connects Liquid to Bitcoin’s mainnet.
The white hat question
On-chain messages from the recipient address claimed the actors were white hats, security researchers who exploit vulnerabilities to expose them rather than profit. They requested direct contact from Blockstream.
As of the latest available reports, zero BTC has been returned.
The peg mechanics and what’s at risk
Technically, the remaining L-BTC in circulation should still be backed 1:1 by BTC because a corresponding volume of L-BTC was burned before the Bitcoin left the reserves. The accounting works on paper: fewer L-BTC outstanding, fewer BTC in the vault, ratio intact.
With only about 197 BTC sitting in federation reserves, the network has almost no buffer to handle redemption demand if peg-outs reopen.
One silver lining: other assets on the Liquid Network, including USDT and tokenized securities, appear unaffected. The bug was specific to the BTC peg-out mechanism, so non-BTC assets hosted on the sidechain weren’t exposed to the same vulnerability.
Broader implications for federated sidechains
Liquid has long occupied a niche position in Bitcoin’s ecosystem. It’s a federated sidechain, meaning a consortium of companies collectively manages the bridge between Liquid and Bitcoin’s mainnet. The vulnerability wasn’t in the cryptographic keys or the federation’s signing process. It was in the node software itself, a layer of infrastructure that most users probably assumed was battle-tested given Liquid has been operational since 2018.
Disclosure: This article was edited by Editorial Team. For more information on how we create and review content, see our Editorial Policy.
English (US) ·