Liquid Network Update: Emergency Elements Patch Released After $320M Exploit
The Liquid Network has released an emergency software update as developers work to restore normal operations following last week’s major security incident. The new Elements v23.3.4 release addresses the proof-verification cache vulnerability linked to the unauthorized creation and withdrawal of roughly 4,000 BTC.
Emergency Elements Patch Targets the Vulnerability
Blockstream said on September 9 that Elements v23.3.4 is now available and that Liquid functionary nodes are being updated immediately. Node operators have also been urged to install the release as the network works through its recovery process.
The patch specifically hardens the cache keys used for range proofs. The Elements GitHub release confirms that v23.3.4 includes changes designed to strengthen range-proof cache handling and adds an option to disable the range-proof cache.
The security issue became critical after attackers exploited the verification weakness and created approximately 4,000 unbacked LBTC. Those assets were subsequently converted through Liquid’s peg-out infrastructure, contributing to the withdrawal of roughly $320 million worth of Bitcoin from the federation-controlled reserves.
Related: Liquid Network Hack Explained: How an Elements Bug Led to a $320M BTC Loss
The incident did not involve the theft of Liquid federation private keys, according to the network’s earlier disclosure. Instead, the exploit demonstrated how a transaction that passed the affected verification process could move through infrastructure responsible for processing Liquid transactions and Bitcoin withdrawals.
Elements v23.3.4 has reportedly gone through several rounds of internal and external review. Blockstream said reviewers included the Bitcoin Red Team and Alpen Labs, reflecting the heightened scrutiny surrounding the emergency release.
The timing of the patch is important because Liquid remains in an unusual operating state. Rather than immediately reopening every network function, Blockstream is separating the technical recovery into stages designed to reduce the risk of repeating the incident.
Liquid Recovery Plan Moves Into Testing
The first planned stage is to resume block production while keeping peg operations suspended. This would allow the blockchain itself to begin operating again without immediately reopening the mechanism that moves Bitcoin between the Liquid sidechain and the Bitcoin network.
The second stage involves replaying transactions that have been verified as valid. Blockstream said it is testing the procedures for the first two stages in parallel, although the final sequence could change depending on testing and validation results.
Peg operations would return only after the network state has been fully restored and the recovery of funds has been addressed. Liquid’s architecture uses functionaries to produce blocks and manage the Bitcoin peg, making the separation between normal block production and peg operations particularly important during the recovery.
The recovery process could therefore take longer than simply installing the new software. Developers and functionaries need to establish that the patched system is behaving correctly, determine which transactions can safely be replayed and confirm that the restored network state is consistent.
For Liquid users, the immediate lesson is to treat unofficial recovery instructions with caution. The network has warned about scammers creating fake update websites and attempting to use the incident to obtain funds, private keys or seed phrases.
Liquid is a Bitcoin sidechain designed for faster settlement, confidential transactions and digital-asset issuance, so restoring trust in its security model is as important as restoring transaction processing.
The release of Elements v23.3.4 marks a significant technical step, but it is not the end of the recovery. For the Liquid community, the next milestones will be the safe return of block production, validation of the transaction replay process and, eventually, the reopening of peg operations.
About The Author
