Liquid Restarts Block Production but Keeps Transactions Frozen

Liquid Network resumed block production on September 10 after deploying emergency software updates, a partial restart following the withdrawal of roughly 4,000 bitcoin from its federation wallet. The network is producing blocks without transactions while operators monitor stability.

The distinction between block production and normal service is critical. Functionary nodes are again signing and validating the chain, showing that the federation can coordinate after the incident. Users still cannot rely on ordinary transfers, and peg operations between bitcoin and Liquid Bitcoin remain suspended. The network is alive, but its economic bridge is not fully open.

Liquid traced the incident to a proof-verification cache vulnerability in Elements, the open-source software underlying the sidechain. An emergency update, Elements v23.3.4, hardened the relevant cache keys used for range proofs. Operators deployed required updates to functionary and bridge nodes before restarting validation.

Actors describing themselves as white hats had withdrawn about 4,000 bitcoin, representing roughly 95% of the federation wallet’s balance at the time. They later returned 3,400 bitcoin after affected bridge nodes were patched. Approximately 598 bitcoin, worth around $46 million at the September 10 market price, remained outstanding.

The white-hat description remains a claim, not an established legal or technical conclusion. Returning most funds reduces the immediate financial shortfall, but it does not erase the exploit or identify who controlled the withdrawn assets. Liquid has not said when the remaining bitcoin will return or who will absorb a loss if it does not.

The incident exposed a central risk in federated sidechains. Liquid is designed to give Bitcoin users faster settlement, confidential transfers and token issuance, but the peg depends on a group of functionaries, bridge software and operational controls. A bug can therefore threaten backing even when Bitcoin’s own consensus and private keys are not compromised.

Restarting in stages is prudent. Producing empty blocks lets operators verify consensus and node behaviour without reopening value transfer immediately. Restoring transactions too early could create inconsistent state or another path to loss. Keeping the network frozen also imposes costs on exchanges, traders and issuers that rely on Liquid liquidity.

The next evidence to watch is concrete: restoration of ordinary transactions, restoration of peg-ins and peg-outs, reconciliation of BTC and L-BTC reserves, publication of a detailed post-mortem and recovery of the outstanding funds. Independent review of the patch would strengthen confidence more than assurances alone.

Why it matters

The restart materially changes the earlier story because Liquid has moved from a complete halt to functioning consensus. It does not mean the network has returned to normal. The most sensitive operations remain closed, and a large amount of bitcoin is still outside the federation wallet.

For users, the episode is a reminder that a bitcoin-denominated asset on a sidechain inherits additional software and governance risk. For developers, it illustrates why caches and proof validation must be treated as consensus-critical. For institutions considering tokenized assets on Liquid, reserve reconciliation, incident transparency and staged recovery will determine whether confidence can be rebuilt.

Sources: Liquid Network recovery update on X · Cointelegraph report · Earlier incident report