
Liquid Network Resumes Block Production After $320M Bitcoin Withdrawal
Liquid Network restarted block production Thursday after a $320 million Bitcoin withdrawal halted the sidechain. The incident drew down reserves by 95%, exposing vulnerabilities in the federated consensus model underlying the network.
Written by CoinArticle’s AI Newsroom · from 2 cited sources. How we work
Outage and Recovery
Liquid Network halted and then resumed block production Thursday following a $320 million Bitcoin withdrawal that depleted its reserves by 95%, according to updates from the sidechain's operators. Functionary nodes—the validators responsible for confirming transactions—began producing blocks again, though the network did not immediately process pending transactions during the initial restart phase.
What the Incident Exposed
The withdrawal and subsequent halt highlight structural vulnerabilities in Liquid's federated consensus design, where a limited set of functionaries control block production and asset custody. The near-total reserve drawdown in a single event raises questions about the adequacy of Liquid's security model and the concentration risk inherent in sidechain architectures that rely on a federation rather than a dispersed validator set.
Network Status and Next Steps
The cause of the $320 million withdrawal and the timeline for resuming normal transaction processing were not detailed in available statements. Liquid Network is a Bitcoin sidechain operated by Blockstream and used primarily for faster settlement and confidential transactions among institutional participants and exchanges.
Why It Matters
For Traders
Liquid liquidity and transaction throughput remain uncertain while the network stabilizes; exposure to wrapped Bitcoin (L-BTC) carries heightened counterparty risk.
For Investors
The incident demonstrates that federated sidechains face trust and security trade-offs that fully decentralized Layer 2 solutions avoid, potentially shifting market preference.
For Builders
Projects relying on Liquid for settlement or liquidity should review contingency plans; the incident underscores why sovereign rollups with decentralized sequencers are architecturally preferable for some use cases.
This article is for information only and is not financial advice. Read the full disclaimer.





