What happened
On 3 November 2026, the Liquid Federation said its bitcoin reserve had been restored to full one-to-one backing for every LBTC in circulation. The announcement followed deposits that closed a gap of about 600 BTC left by a September software exploit. Liquid's public dashboard now lets anyone compare the federation's bitcoin holdings with the amount pegged into the sidechain, while node operators can verify the reserve through their own software.
Liquid is a federated Bitcoin sidechain. A user locks bitcoin with the federation and receives LBTC on a separate network. The system is designed so that one LBTC can be exchanged for one BTC, but that promise depends on both sufficient reserves and a working withdrawal route.
The shortfall began on 6 September. Blockstream's incident assessment says a flaw in the Elements range-proof verification cache let an attacker create about 4,000 LBTC without matching inputs. The attacker used those unbacked units through a member's authorized peg-out route and withdrew about 4,000 BTC. Roughly 3,400 BTC was returned the next day, leaving about 600 BTC outstanding.
The technical fix shipped in Elements 23.3.4 on 9 September. It hardened the cache keys and added a way to disable the affected cache. Fixing the validation bug stopped the same path from being reused. It did not by itself replace the missing bitcoin.
What it changes
The reserve deficit is closed. At the system level, circulating LBTC is no longer backed by less bitcoin than the federation says it represents. That matters because a token can continue trading while its reserve is short, but a one-to-one redemption promise cannot be met for everyone unless the missing assets are restored.
Users also have a practical route between BTC and LBTC again through participating swap providers. SideSwap says its peg-in and peg-out services are open, although its payouts use its own bitcoin wallet and may require manual refilling. That is not the same mechanism as a direct federation peg-out.
The recovery also makes the reserve claim independently checkable. A public balance is more useful than a promise without a number, and a Liquid node can verify the federation wallet against issuance. This proves a narrow fact: whether the visible bitcoin reserve matches the visible LBTC supply at the time checked.
What it does not change
The restoration does not make LBTC the same asset as bitcoin held under the user's own keys. LBTC still depends on a federation, separate consensus software and authorized routes back to Bitcoin. A full reserve removes one failure state, not those trust and operational dependencies.
The federation's announcement did not identify who supplied the replacement bitcoin. The Block reported that federation board member Samson Mow attributed it to Blockstream. The official notice itself did not provide a funding breakdown. The claim should therefore remain attributed rather than treated as a reconciled federation account.
Normal withdrawal access is also not fully documented. Swap providers are operating, but the latest official recovery update did not say that direct federation peg-outs had returned without the enhanced controls introduced after the exploit. Equal reserves and unrestricted redemption are separate conditions.
Proof of reserves also does not prove the absence of software bugs, governance failures or future liabilities. It answers whether a stated wallet balance covers a stated circulating supply. September showed that a consensus bug could create an invalid liability before operators stopped the network.
Context
Three independent newsrooms reported the 3 November restoration. CoinDesk separated the closed reserve gap from the still-restricted direct withdrawal route. The Block tracked the deposits and reported Mow's funding attribution. Decrypt confirmed the reserve match and reported additional hardening claims from Blockstream CEO Adam Back.
They agree that one-to-one backing has been restored and that about 600 BTC had remained missing after the attacker returned 3,400 BTC. They differ mainly on how confidently the replacement funds can be attributed. The reserve repair is complete by the published balance, while the source of funds, direct federation withdrawal status and promised governance changes remain less complete.