Liquid

Read

Bitcoin

<p>Liquid Network has resumed block production without processing transactions after a $320 million Bitcoin withdrawal forced the sidechain to halt operations.</p>
<div id="cn-block-summary-block_837b73b53ae4992671ad39ab23b445f0" class="cn-block-summary">
 <div class="cn-block-summary__nav tabs"><span>Summary</span>
 </div>
 <div class="cn-block-summary__content">
  <ul>
   <li>Functionary nodes have resumed signing and validating blocks after receiving required software updates.</li>
   <li>Transactions and BTC peg operations remain suspended while Liquid monitors the network.</li>
   <li>Hackers returned 3,400 BTC, leaving about 598 BTC outside the federation wallet.</li>
   <li>Elements v23.3.4 changes how the software verifies and stores confidential transaction proofs.</li>
  </ul>
 </div>
</div>
<p>Liquid Network said in a Thursday <a href="https://x.com/Liquid_BTC/status/2098025275921490281" rel="noopener noreferrer nofollow">update</a> that its functionary nodes were again producing blocks as intended, but the network would operate “without transactions” while developers monitored its condition.</p>
<p>The limited restart allows Liquid to test its updated infrastructure without reopening transfers or exposing the peg system to new activity. According to the network, keeping transactions disabled will help operators “confirm full stabilization” before they restore other services.</p>
<p>Functionary and bridge nodes have received the required software changes, Liquid added. Its functionaries can now sign and validate blocks, though users cannot yet send regular transactions or move funds between Bitcoin and Liquid.</p>
<p>Peg operations also remain suspended, including withdrawals approved through Peg-out Authorization Keys, or PAKs. Liquid said the restrictions would stay in place while it works to restore the reserve that supports Bitcoin issued on the sidechain as L-BTC.</p>
<p>You might also like: <a href="https://crypto.news/liquid-network-320-million-drain-cache-bug-unbacked-bitcoin/" rel="noopener noreferrer nofollow"> Liquid Network drained of $320 million as cache bug lets attacker mint unbacked Bitcoin </a></p>
<h2 class="wp-block-heading" id="liquid-network-has-restarted-with-transactions-disabled">Liquid Network has restarted with transactions disabled</h2>
<p>Block production represents only one part of Liquid’s return to service because its transaction and bridge systems remain unavailable. The network has not provided a date for reopening either function.</p>
<p>Under normal conditions, users deposit BTC into the federation-controlled peg and receive an equal amount of L-BTC for use on Liquid. Holders can later burn L-BTC through an approved peg-out service to release the corresponding Bitcoin on the base layer.</p>
<p>Operators stopped that process after an actor created unbacked L-BTC by exploiting a proof-verification flaw in Elements, the open-source software behind Liquid. The actor then submitted the tokens through SideSwap’s authorized peg-out service, prompting the federation to release real Bitcoin.</p>
<p>As <a href="https://crypto.news/liquid-network-320-million-drain-cache-bug-unbacked-bitcoin/" rel="noopener noreferrer nofollow">crypto.news previously reported</a>, the transaction removed about 3,996 BTC and reduced the federation wallet from approximately 4,205 BTC to about 202 BTC. The withdrawal represented roughly 95% of the Bitcoin held in the wallet at the time.</p>
<p>Liquid described the actors as “purported white-hat hackers” after they identified themselves as white hats through messages attached to Bitcoin transactions. Their claim did not establish that they had permission to create the L-BTC or withdraw the underlying Bitcoin.</p>
<p>SideSwap said a customer had sent 4,000 L-BTC to its peg-out service, which processed the request under its normal system. Liquid and SideSwap said the key used to authorize the transaction had not been compromised.</p>
<h2 class="wp-block-heading" id="elements-update-changes-proof-verification-cache">Elements update changes proof-verification cache</h2>
<p>One day before restarting block production, Liquid released an emergency Elements <a href="https://x.com/Liquid_BTC/status/2097695714310521331" rel="noopener noreferrer nofollow">update</a> designed to address the flaw connected to the withdrawal.</p>
<p>Elements v23.3.4 changes the cache keys used when validating range proofs, according to Liquid. Range proofs allow the network to confirm that a hidden transaction amount is valid without publicly revealing the amount, forming part of Liquid’s confidential transaction system.</p>
<p>The affected software stored successful proof-verification results so nodes could reuse them instead of repeating the full calculation. Previous reporting found that the cache did not include enough transaction context, allowing a valid proof result to be reused where it should have failed.</p>
<p>By exploiting that weakness, the actor created L-BTC without first locking an equal amount of Bitcoin in the federation wallet. Functionary nodes running the affected code accepted the tokens, while SideSwap’s peg-out process treated them as valid L-BTC and processed the withdrawal.</p>
<p>Liquid said version 23.3.4 hardens the cache keys associated with range proofs. Functionary and bridge nodes received the update before block signing restarted, although the network is still withholding transactions while operators check the deployment.</p>
<p>Liquid’s federation uses functionary nodes to confirm sidechain blocks and control the Bitcoin held behind L-BTC. The system relies on 15 rotating functionaries and requires 11 signatures to move funds from its multisignature wallet, according to an earlier technical account of the incident.</p>
<p>No federation signing key was reported stolen during the withdrawal. The failure instead involved the software used to decide whether the L-BTC submitted for redemption was valid.</p>
<h2 class="wp-block-heading" id="hackers-returned-3-400-btc-after-nodes-were-patched">Hackers returned 3,400 BTC after nodes were patched</h2>
<p>Communication between Blockstream and the actors took place through messages embedded in Bitcoin transactions. In one message, the actors said they would return the assets after the vulnerable nodes had been repaired.</p>
<p>“Please fix the bug first,” the message said. “Make sure every node is patched. Then we will transfer the money back safely after confirming the fix.”</p>
<p>Blockstream later sent a signed message stating that its bridge nodes had been patched and that the Bitcoin was “safe to return.” Following that confirmation, the actors transferred 3,400 BTC back to the federation wallet.</p>
<p>The <a href="https://crypto.news/liquid-network-recovers-3400-btc-after-bridge-exploit/" rel="noopener noreferrer nofollow">3,400 BTC repayment</a> restored about 85% of the withdrawn funds. At the time of the transfer, the returned Bitcoin was worth approximately $270 million.</p>
<p>About 598.5 BTC remained in the withdrawal-linked address after the repayment. The outstanding balance was worth roughly $46 million based on the Bitcoin price cited in the supplied report, though its dollar value changes with the market.</p>
<p>No public agreement has identified the remaining Bitcoin as an approved security bounty. The actors have not publicly stated whether they plan to return another portion, while Blockstream has not announced terms allowing them to keep the balance.</p>
<p>Ledger Chief Technology Officer Charles Guillemet questioned the white-hat label after the partial repayment. In an X post, he argued that retaining about 600 BTC without publicly disclosed terms looked more like extortion than a standard security reward.</p>
<h2 class="wp-block-heading" id="l-btc-holders-await-restoration-of-peg-services">L-BTC holders await restoration of peg services</h2>
<p>Liquid operates as a federated Bitcoin sidechain that allows exchanges, trading firms and other users to transfer BTC-linked assets with shorter settlement times than Bitcoin’s base layer. Blockstream launched the production network in 2018 using Elements software.</p>
<p>L-BTC depends on Bitcoin held in the federation wallet to maintain its one-to-one backing. Until Liquid restores peg operations, holders cannot use the normal bridge process to redeem L-BTC for native Bitcoin.</p>
<p>A previous <a href="https://crypto.news/how-cross-chain-bridges-work-and-why-4-billion-has-been-stolen-from-them/" rel="noopener noreferrer nofollow">bridge security explainer</a> described how systems that lock assets on one chain and issue linked tokens on another depend on their custody, validation, and message-processing controls. A failure in any part of that process can suspend redemptions even when the underlying blockchain continues to operate.</p>
<p>For U.S. users, the current effect is limited to access and operations rather than a stated change in federal policy. American L-BTC holders face the same transaction and peg restrictions as users elsewhere, while BTC held directly on Bitcoin’s base layer remains separate from the Liquid system.</p>
<p>No U.S. regulator or law enforcement agency has announced an action connected to the withdrawal. Liquid also has not given a timetable for restoring transactions, PAK-authorized peg-outs, or other bridge operations.</p>
<p>Read more: <a href="https://crypto.news/ethfi-price-targets-0-75-after-range-breakout/" rel="noopener noreferrer nofollow"> ETHFI price targets $0.75 after range breakout </a></p>

Liquid Network resumes blocks after $320M Bitcoin withdrawal

Table of Contents

crypto.news

Other articles published on Sep 10, 2026

Join our free newsletter for daily crypto updates!