Liquid Sidechain Paused After ~4,000 BTC Withdrawn From Federation Reserves
Blockstream's Liquid Network was paused Sunday after nearly all bitcoin reserves backing L-BTC were withdrawn to a single address by parties claiming to be white-hat hackers. Bridge nodes were disabled and the sidechain halted pending investigation.
Written by CoinArticle’s AI Newsroom · from 2 cited sources. How we work
The Withdrawal and Network Halt
Blockstream disabled Liquid Network's bridge nodes on Sunday after approximately 4,000 bitcoin left the federation wallet that backs L-BTC, the sidechain's wrapped bitcoin asset. Bitcoin Magazine reported the figure as 4,000 BTC, while The Defiant cited 3,998 BTC withdrawn to a single address. The parties behind the withdrawal included a message in a bitcoin transaction stating "we are whitehats," suggesting they claimed to be acting in the network's security interest rather than as malicious actors.
Blockstream responded by halting the sidechain entirely, disabling the bridge infrastructure that allows assets to move between Liquid and the Bitcoin main chain. The move effectively froze all L-BTC redemptions and new deposits pending further investigation into the withdrawal.
What Remains Unclear
Neither source provided details on how the withdrawal occurred, whether it exploited a specific technical vulnerability, or what Blockstream's investigation timeline might be. The federation wallet typically requires multiple signatures to authorize transactions, raising questions about whether the withdrawal was authorized by insiders or represented a breach of the multisig scheme. Blockstream has not yet published a technical postmortem or security advisory.
Why It Matters
For Traders
L-BTC trading and redemptions are halted until the sidechain resumes; holders cannot exit positions via the bridge and should monitor exchange listings for liquidity.
For Investors
The incident exposes risks in federated sidechain security models and may accelerate discussion around custodial versus non-custodial wrapped asset designs.
For Builders
Liquid-based dApps are offline until the network restarts; teams should prepare contingency plans for extended outages and consider bridge redundancy in architecture.
This article is for information only and is not financial advice. Read the full disclaimer.
