Liquid Network Restores 1:1 Bitcoin Backing for LBTC After September Exploit
Key Highlights
- The Liquid Federation announced on November 3 that its Bitcoin reserves had been fully restored, reestablishing 1:1 backing for all LBTC.
- Final deposits on November 2, including a 250 BTC transfer, closed the remaining reserve gap.
- Samson Mow said another 50 BTC had been added in an earlier update, leaving 550 BTC to be replenished at that stage.
The Liquid Federation has announced that the Bitcoin reserves backing Liquid Bitcoin (LBTC) are fully restored, reestablishing the token’s 1:1 backing with Bitcoin.
In a November 3 post on X, the Liquid Federation said it had replenished its Bitcoin reserves, restoring full BTC backing for all LBTC in circulation.
The announcement confirms the completion of the reserve replenishment process following the September exploit. The Federation also outlined plans for further governance and security changes, with more details expected in the coming weeks.
What the Federation announced
The Federation said the restoration follows the resumption of BTC-LBTC swaps several weeks earlier, allowing users to move between Bitcoin and Liquid at a 1:1 rate through participating swap providers.
It added that the reserves remain independently verifiable. Users running their own Liquid nodes can check the Federation’s Proof of Reserves directly, while others can monitor reserve balances and network activity through the Liquid Network dashboard.
The Federation also plans to modernize its governance structure, establish clearer responsibilities and oversight, and introduce additional technical and operational safeguards.
Final deposits closed the reserve gap
The restoration was completed through a series of transfers into the Federation wallet. According to reports, four deposits totaling approximately 602.5 BTC completed the replenishment, including a final 250 BTC transfer on November 2. After that transfer, Mempool’s Liquid explorer data showed 4,268.95 BTC in reserves against 4,268.95 LBTC in circulation.
The Federation’s November 3 announcement did not identify the source of the replenishment funds or provide a detailed breakdown of the individual contributions.
Samson Mow clarifies peg-out availability
In an October 28 post on X, Liquid Federation board member Samson Mow said another 50 BTC had been added to the reserves, leaving 550 BTC to be replenished at that stage. He also disputed reports suggesting that peg-outs would resume only after the entire reserve shortfall had been replenished.
Mow said the Federation had been conducting semi-automated peg-outs for its members for more than a week. He added that end users of AQUA, SideSwap and Bull Bitcoin had already been able to convert LBTC back into BTC through those providers during that period.
His comments distinguish between semi-automated Federation operations and user-facing services available through participating providers.
How the Liquid Network exploit happened
The reserve restoration follows an exploit on September 6, 2026, that affected the Liquid Network, a Bitcoin sidechain operated through the Liquid Federation.
In an earlier report, The Crypto Times covered how the network was paused after an exploit created a reserve shortfall involving approximately 4,000 BTC worth of unbacked LBTC. The incident involved a vulnerability in Elements, the open-source software underlying Liquid.
On September 11, SlowMist’s technical analysis traced the exploit to a rangeproof cache collision. According to the security firm, the flaw bypassed verification checks and enabled the creation of approximately 3,998.5 unbacked LBTC. The flaw affected Elements’ rangeproof verification process. The incident led the Federation to suspend network operations while it investigated and addressed the issue.
White Hat returned 3,400 BTC, retained 598.5 BTC
The recovery process included the return of part of the Bitcoin associated with the exploit.
On September 8, The Crypto Times reported that a person claiming to be a white-hat hacker had returned approximately 3,400 BTC to the Federation. The individual retained 598.5 BTC, representing roughly 15% of the Bitcoin involved in the incident, and indicated that the amount could serve as a bounty.
The returned Bitcoin reduced the reserve shortfall, but full backing had not been restored at that stage.
Liquid Network restarted before full reserve restoration
The Federation resumed Liquid Network operations on September 10, following the exploit and initial recovery efforts.
In its September 10 coverage, The Crypto Times reported that the network had restarted. Blockstream CEO Adam Back said the LBTC peg would be covered, although the reserves had not yet been fully restored.
Network operations therefore resumed while the reserve replenishment process was still underway.
Governance and security changes still to come
The Federation plans to provide further details on changes to its governance structure, oversight arrangements and technical and operational safeguards in the coming weeks.
These measures are intended to address the governance and security issues raised by the September exploit. The Federation has not yet provided a detailed implementation plan or timeline.
Also Read: Binance Lacks Cyber Insurance for $6.3B Hack — So Who Pays for the Losses?
Disclaimer: The information researched and reported by The Crypto Times is for informational purposes only and is not a substitute for professional financial advice. Investing in crypto assets involves significant risk due to market volatility. Always Do Your Own Research (DYOR) and consult with a qualified Financial Advisor before making any investment decisions.


