Liquid Federation Restores Full 1:1 Bitcoin Backing for LBTC

The Liquid Federation says the bitcoin reserves behind its LBTC token are fully restored, nearly two months after a software flaw drained most of them. In a post on X early on 3 November, the group of companies that runs the Liquid sidechain said “the network’s bitcoin reserves have been fully restored, reestablishing 1:1 BTC backing for all LBTC”, and that the backing can be checked by anyone through node-level Proof of Reserves and the public dashboard at liquid.network.

That claim is independently checkable, and it checks out. On the morning of 3 November the liquid.network dashboard showed the federation’s BTC holdings matching the LBTC in circulation — about 4,270 of each — with a reserve surplus of zero, the on-chain signature of a peg that is neither short nor padded. The federation said one-to-one swaps between BTC and LBTC through participating providers had resumed “several weeks ago”.

What the Liquid Federation has said

The federation framed the restoration as a milestone rather than the end of the work. It said the one-to-one peg was back, pointed users to on-chain verification, and set out what comes next: modernising governance, clearer responsibilities and oversight, and more technical and operational safeguards, with details promised “in the coming weeks”. It did not detail the final steps of the reserve top-up, and this piece makes no claim about where the closing bitcoin came from.

For a token that only has value because each unit is meant to be backed by real bitcoin, the restored peg is the headline. LBTC is a wrapped representation of bitcoin on the Liquid sidechain; if the reserves behind it fall short, the token is worth less than the bitcoin it claims to stand for. That is the strain that has felled other bitcoin-wrapper products this year, including the recent pause on tBTC minting.

How the peg can be verified on-chain

The more durable reassurance is not the statement but the data. The liquid.network dashboard publishes the federation wallet’s live bitcoin balance against the circulating LBTC supply, and any Liquid node operator can run the same Proof of Reserves check independently. On 3 November both sides read the same number, about 4,270, with the “reserve surplus” line at zero — meaning the reserves exactly cover the tokens in issue. It is the kind of claim that does not depend on trusting the issuer’s word.

Adam Back’s three hardened defences

Adam Back, who leads Blockstream, the company behind Liquid’s technology, set out on X what he called three lines of defence that have been hardened. The peg-out authorisation keys that control withdrawals have been refreshed and moved into cold hardware wallets. The proof-validation caches that the original attack abused have been disabled and the underlying node bug fixed. And the consensus rules have been hardened to “fail closed”, so that a node now rejects anything it cannot fully validate rather than waving it through. Back said the changes had been through multiple third-party audits, and drew a broader lesson for engineers — to treat AI-suggested fixes with suspicion, summed up as “don’t trust, verify”.

What happened in September

The shortfall dates to early September. According to Decrypt, purported white-hat hackers withdrew about 4,000 BTC — worth roughly $320m at the time — from the federation wallet, returned about 3,400 BTC the following day, and kept around 598 BTC. TSN has described the people involved as purported white hats because their status has not been established; the federation has not characterised them, and no court or law-enforcement finding has been reported.

Why on-chain proof matters more than the announcement

An exchange or issuer saying it is solvent is worth little on its own; crypto is littered with such assurances that later proved hollow. What makes the Liquid Federation’s claim different is that it is falsifiable in public, block by block, by anyone who cares to look. That is the whole design argument for a bitcoin sidechain with Proof of Reserves: the backing is not a quarterly attestation but a live figure. On a day when the dashboard shows holdings equal to supply and a zero surplus, the “1:1” is not marketing — it is the current state of the chain.

Two caveats keep this short of a clean bill of health. Direct federation peg-outs have run under enhanced controls since the incident, and the promised governance overhaul is still just a promise, with detail owed “in the coming weeks”. And the federation’s silence on how the last stretch of the shortfall was filled leaves a provenance question open even with the peg whole — reserves can be restored by very different means, and which one was used matters for how robust the fix really is. Set against a year in which crypto losses have run into the billions, as tracked by Hacken, a verifiable return to full backing is a better outcome than most hacked projects manage, even if it is not the end of the story. The near-$6bn Binance incident that TSN covered last month is a reminder of how rarely stolen funds come back at all.

What to watch now: whether the federation publishes the promised governance detail on schedule, and whether direct peg-outs reopen fully once it does.

Sources

• Liquid Federation, @Liquid_BTC on X (3 November 2026)
• Liquid Network Proof of Reserves dashboard, liquid.network
• Adam Back, @adam3us on X
• Decrypt, “Liquid Network Restores Full Bitcoin Backing Two Months After $320M Exploit”

Related stories

• Hacken: Crypto Hacks Cost $1.18bn in Q3 2026, Mostly via Suppliers
• Threshold Pauses tBTC Minting as Aave Halts New tBTC Deposits