# Liquid Network Enters Final Recovery Stage a Month After Consensus Bug Drained 4,000 Bitcoin

Attackers who say they are white hats returned about 3,400 BTC and kept roughly 598 BTC, so Blockstream's sidechain is still short of full one-to-one backing as swaps resume in phases.

- Published: 2026-10-21T05:37:25.162Z
- Canonical: https://polylog.news/crypto/2026-10-21/liquid-network-enters-final-recovery-stage-a-month-after-con
- Publisher: Polylog (Crypto desk)
- Section: crypto
- Sources: [Bitcoin Magazine](https://bitcoinmagazine.com/news/liquid-network-announces-recovery), [Blockstream](https://blog.blockstream.com/liquid-network-security-incident-assessment/), [CoinDesk](https://www.coindesk.com/markets/2026/09/08/white-hat-hackers-return-most-of-usd320m-bitcoin-taken-from-liquid-network), [The Block](https://www.theblock.co/news/defi/2026-09-07-liquid-network-attacker-says-they-will-return-most-of-4000-btc-after-bug-fix-413673)

The Liquid Network, the Bitcoin sidechain built by Blockstream and used by exchanges and trading desks, [says it is running again and in the final stages of recovery](https://bitcoinmagazine.com/news/liquid-network-announces-recovery). Attackers took about 4,000 BTC from its federation wallet in September. Swaps between bitcoin and Liquid bitcoin (L-BTC) have resumed in phases while the operators work to restore full one-to-one backing.

The attack started with an inflation bug in Elements, the open-source codebase Liquid runs on. According to [Blockstream's incident assessment](https://blog.blockstream.com/liquid-network-security-incident-assessment/) and outside analyses, a verification cache did not record the asset and script context of proofs it had already checked. The attackers reused a proof that had been verified in one context to validate a new, unauthorized issuance. They minted about 4,000 L-BTC that had no backing and then redeemed it for real bitcoin through the federation's peg-out process, which sends bitcoin back to the main chain. Blockstream says no signing keys were compromised. Under the faulty consensus rules the withdrawal looked valid, so the federation's signing servers approved it.

The attackers then negotiated in public. They wrote messages into Bitcoin transactions and told Blockstream to [fix the bug and patch every node before they returned anything](https://www.theblock.co/news/defi/2026-09-07-liquid-network-attacker-says-they-will-return-most-of-4000-btc-after-bug-fix-413673). Blockstream answered with a signed on-chain message saying the bridge nodes were patched. The group [returned about 3,400 BTC](https://www.coindesk.com/markets/2026/09/08/white-hat-hackers-return-most-of-usd320m-bitcoin-taken-from-liquid-network) and kept about 598 BTC, roughly 15% of the total, as a bounty it set for itself. The theft was worth about $320 million at the time.

The shortfall is the open question for L-BTC holders. A wrapped bitcoin is worth only what its custodian can redeem. Until the missing 598 BTC is covered, L-BTC is backed by less than one bitcoin per token.

## What this means

Liquid's federation of exchanges and custodians is the security model institutions chose because it avoids smart-contract risk. In this case the signers worked exactly as designed and approved a withdrawal that the faulty consensus rules said was valid. Exposure sits with L-BTC holders, who carry the shortfall until someone covers it, and with every multisig or federated bridge whose signers check transaction validity with the same software that produces it. Most commentary treated the return of 3,400 BTC as the end of the story. The more important consequence is that a negotiated bounty of about 15% now exists as a working template for attackers. The 2021 Poly Network exploit ended the same way, with an attacker returning funds after taking a cut, and later attackers cited it. The likelier outcome over the next several months is that federations and bridges add independent validation, such as a second implementation or separate software that checks supply limits, before they sign any peg-out. That depends on Blockstream publishing a full root-cause analysis. If Blockstream declares the incident closed without one and without explaining how the remaining 598 BTC will be covered, this read is wrong, and the market will price L-BTC at a discount to bitcoin.

## What to watch

- How Blockstream or the federation members say they will fill the 598 BTC hole. This decides whether L-BTC returns to full backing or trades permanently below bitcoin.
- Publication of a full technical post-mortem of the Elements bug. Other sidechains and bridges built on the same code need it to check their own exposure.
- Whether the retained bitcoin moves on-chain toward exchanges or mixers. A move like that would test whether the attackers' "white hat" claim holds.