Liquid Network, the Bitcoin sidechain operated by the Blockstream-led Liquid Federation, is reported to have halted after purported white-hat hackers withdrew roughly $320 million in Bitcoin from the federation’s wallet, according to an official September 6, 2026 statement and subsequent reporting.
Liquid Network, the Bitcoin sidechain operated by the Blockstream-led Liquid Federation, is reported to have halted after purported white-hat hackers withdrew roughly $320 million in Bitcoin from the federation’s wallet, according to an official September 6, 2026 statement and subsequent reporting. The Liquid Network halt and the size of the reported loss remain, in key respects, approximate estimates rather than a verified final accounting.
The starting point is the network’s own words. Liquid Network’s September 6 post acknowledged a security incident and said Blockstream was working to contact the actors on-chain with a signed message, per the official statement. The visible excerpt confirms the incident and the approximate figures but truncates before operational detail. For related coverage, see Liquid Recovers 3,400 BTC: Bitcoin Recovery Details.
What Is Known About the Reported Liquid Network Halt?
The affected entity is the Liquid Federation wallet, the multi-signature reserve backing Liquid Bitcoin (L-BTC), the sidechain’s Bitcoin-pegged asset. The alleged event concerns network operation, not a single exchange service, and our coverage of the reported network halt traces the same distinction.
The pause itself is not visible in the official excerpt. Protos, in a September 7 report, attributes to Liquid Network the statement that the sidechain was paused until resolution, with bridge nodes disabled and exchanges suspending L-BTC deposits and withdrawals, according to that reporting. That establishes an incident-time pause, not present operating status.
Whether the network remains halted is, according to unconfirmed reports, still the case at research completion, but no official restart notice was verified. The incident date is anchored to the September 6 statement; a confirmed end-to-end timeline and a current attributable status statement remain unknown.
What Supports the Reported $320 Million Bitcoin Loss?
The core figure comes directly from the protocol. Liquid Network’s statement reported an approximate withdrawal of about 4,000 BTC, valued there at the headline dollar sum, and both are described as source estimates rather than an independently calculated net loss.
Reported withdrawal from the Liquid Federation wallet
~4,000 BTC
A dollar valuation is not the same as an asset quantity. The reported Bitcoin amount and its dollar value are both approximate, and the exact incident-time BTC/USD exchange rate used to derive the figure was not disclosed. Our assessment of the loss claim keeps both numbers in approximate terms for that reason.
Root cause remains attributed, not proven. Protos reports that SideSwap blamed faulty L-BTC originating from a third-party Elements bug and denied that its own systems were responsible; that attribution is not an independently verified cause. Elements is the open-source codebase underpinning the Liquid sidechain. A specific validation flaw, with no federation signing key compromised, is described only according to unconfirmed reports.
Reports of repayment should also be treated with caution. Claims that attackers returned a large share of the funds, echoed in our note on the reported return of 3,400 BTC, rest on unconfirmed later headlines rather than a directly fetched transaction. Attacker identity, the exploit mechanism, and any causal link between the hack and the halt all still require evidence.
For scale, the reported withdrawal dwarfs recent throughput. The Liquid Federation’s Q1 2026 update reported 1,201 peg-outs totaling 1,144 BTC across the quarter, though quarterly throughput measures activity, not reserve coverage.
What Remains Unknown for Liquid Network Users?
Transaction availability, the safety of affected funds, and any restoration timing are the unresolved questions. No service notice, recovery plan, restart estimate, or compensation detail was verified, and the situation matches our tracking of the reserve drawdown.
No claim can yet be made that funds are safe, that funds are lost, that operations have resumed, or that compensation is available. Users should treat incident-specific guidance as pending until an attributable official notice appears.
Industry reaction has centered on maintenance concerns. Jameson Lopp, a Bitcoin security engineer and co-founder of Casa, criticized apparent inactivity in the Liquid functionary codebase; his post also contains speculation about causation that is not evidence.
I seriously doubt it's a coincidence that the Liquid bridge got drained just a couple days after Astra dropped.
Looks like the Liquid functionary codebase hasn't been touched in 2 years, which isn't a good sign.https://t.co/skDn0tHQIg
— Jameson Lopp (@lopp) September 6, 2026
Source: @lopp on X
The event does not register on the Bitcoin base layer’s economics. Bitcoin traded at $78,906, down about 1.1% on the day, with the broader Fear & Greed Index at 69, in Greed territory. Neither reading can be attributed to the Liquid incident, and because Liquid is a sidechain, its federated peg does not affect Bitcoin mainnet hashrate, difficulty, or the fixed 21 million supply schedule that anchors the asset the sidechain is designed to represent.
Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Cryptocurrency and digital asset markets carry significant risk. Always do your own research before making decisions.
