- The Liquid Network, a prominent Bitcoin layer-2 sidechain, was frozen following a white-hat hack that intercepted $320 million in bitcoin.
- The intervention was executed by ethical hackers to prevent a catastrophic exploit, temporarily halting operations across the network.
- Stakeholders are actively working to restore normal functionality and secure user funds as on-chain investigations continue.
The Liquid Network, a leading Bitcoin sidechain and settlement network designed for fast, confidential transactions, was abruptly frozen after a group of white-hat hackers secured approximately $320 million in bitcoin. According to details shared in an official Liquid Network announcement, the emergency freezing mechanism was triggered to thwart a potential malicious exploit that threatened a massive pool of user capital.
The incident unfolded when security researchers identified a critical vulnerability within the network’s architecture. Rather than allowing the exploit to be weaponized by bad actors, the ethical hackers intervened, successfully intercepting and securing roughly $320 million worth of digital assets. In response to the emergency, the federated governance model of the Liquid Network enacted a network-wide halt to evaluate the breach, assess the safety of remaining funds, and coordinate remediation efforts.
Market participants and crypto traders quickly reacted to the sudden freeze, monitoring on-chain movements as developers raced to patch the underlying flaw. Sidechains like Liquid rely on a federation of trusted functionaries rather than standard proof-of-work consensus, giving operators the unique capability to pause block production during critical security events. As highlighted in a statement posted to the official Liquid Network X account, maintaining the integrity and safety of user funds remains the absolute priority for the federation.
Industry analysts point out that while the white-hat intervention successfully averted a historic financial loss, the episode underscores the inherent centralization trade-offs present in federated layer-2 solutions. As development teams work around the clock to deploy comprehensive fixes, the timeline for fully resuming normal network operations and unfreezing user balances depends heavily on the thoroughness of ongoing security audits.
