Skip to content

News Bitcoin

Liquid Network Bitcoin Backing Restored to Full 1:1 After Exploit

Key points

Liquid Network restored full 1:1 Bitcoin backing for LBTC on November 3, 2026, after deposits closed the gap left by the September exploit that drained nearly 4,000 BTC.

Rating 4.9 24 votes
Vector graphic of balanced BTC and L-BTC tokens showing restored 1:1 Liquid Network reserve backing

Liquid Network restored full 1:1 Bitcoin backing for all issued LBTC on or around November 3, 2026. The Bitcoin sidechain Federation confirmed that reserves again matched the outstanding LBTC supply after multiple deposits closed the shortfall created by the September exploit.

Recovery Deposits Close the Reserve Gap

Multiple Bitcoin deposits restored the reserves between late October and early November. These included 50 BTC on October 28, followed by 300 BTC and a final 250 BTC on November 2. Dashboard readings after the deposits showed between 4,268.95 and 4,270.54 BTC held against an equivalent LBTC supply, with the network status labeled as solvent.

Swaps between BTC and LBTC at the 1:1 rate through third-party providers such as SideSwap had resumed in late October. Federation-managed direct peg-outs remain subject to enhanced operational controls. Other assets on the network, including USDt, stayed unaffected throughout the period.

The official Federation statement did not identify the source of the replacement funds. Board member Samson Mow attributed the deposits to Blockstream in public comments. Reserves can be verified on the public dashboard at liquid.network and through node-level Proof of Reserves data.

September Exploit and Initial Response

The shortfall originated from an exploit on September 6, 2026, at approximately 13:53 UTC. A flaw in the rangeproof-verification cache of the Elements software enabled the creation of roughly 4,000 unbacked LBTC. These tokens were redeemed for approximately 4,000 BTC, valued at about 320 million dollars at the time, from the Federation wallet.

Flat vector graphic showing Bitcoin deposits restoring the reserve vault gap
Stepwise Bitcoin deposits completed in early November successfully closed the reserve gap.

Reserves dropped from around 4,205 BTC to 197 BTC immediately after the incident. The attacker, who identified as a white hat, returned roughly 3,400 BTC on September 7 after Blockstream deployed patches to bridge nodes. Approximately 600 BTC remained unrecovered. Blockstream declined a reported demand for a 10 percent bounty.

Liquid operates as a federated Bitcoin sidechain coordinated by Blockstream. It allows faster and lower-cost transfers of BTC through LBTC tokens that were designed to maintain a strict 1:1 peg backed by reserves held in a Federation wallet. No private keys were compromised during the event.

Next Steps for Governance and Controls

The Federation stated it will release further information on governance changes, security upgrades, and revised operational procedures in the coming weeks. The timeline for any adjustments to direct peg-out processes remains subject to those disclosures.

Market participants can monitor reserve levels in real time through the network dashboard and independent node verifications. The restoration brings the peg back to its original design parameters while the Federation continues to operate under heightened scrutiny of its wallet controls.

Frequently asked questions

When did Liquid Network restore full Bitcoin backing?

The Federation confirmed full 1:1 reserves matching LBTC supply on or around November 3, 2026, after final deposits on November 2 closed the remaining gap.

How much BTC was lost in the September exploit?

Roughly 4,000 BTC valued at about 320 million dollars were removed from the Federation wallet on September 6, though 3,400 BTC were later returned.

What caused the Liquid Network exploit?

A rangeproof-verification-cache flaw in the Elements software allowed creation of unbacked LBTC that were redeemed for Federation reserves.

Are BTC to LBTC swaps available again?

Third-party swaps at the 1:1 rate resumed in late October, while direct Federation peg-outs continue under enhanced controls.

Where can reserves be verified?

Reserves appear on the public dashboard at liquid.network and through node Proof of Reserves checks.

Comments

No comments yet. Be the first!

Leave a comment