The Ledger
Liquid Restores 1:1 Bitcoin Backing for LBTC
The Liquid Federation says its bitcoin reserves again fully back all LBTC, following the return of BTC-to-LBTC swaps through participating providers. Direct Federation peg-outs remain subject to enhanced controls, and the update does not say they have resumed.

The Liquid Federation is pleased to announce that the network’s bitcoin reserves have been fully restored, reestablishing 1:1 BTC backing for all LBTC.
Liquid Federation, in a Telegram update
In a Telegram update, the Liquid Federation said its Bitcoin reserves once again cover all LBTC, the Bitcoin-linked asset issued on the Liquid sidechain. The announcement marks a full-backing milestone in the recovery from a September exploit that drained most of the network’s reserve wallet. The Federation said users can verify reserves by running Liquid nodes or checking its public dashboard.
BTC-to-LBTC swaps through participating providers had resumed several weeks earlier, the Federation said. Those swaps let users move between Bitcoin and Liquid at a 1:1 rate, but they are distinct from direct Federation peg-outs. The latest update does not say whether normal direct peg-out operations have restarted.
September’s Elements flaw drained the reserve
On September 6, an attacker exploited a vulnerability in Elements, the open-source software underlying Liquid, to create about 4,000 LBTC without matching Bitcoin backing. Blockstream’s technical assessment traced the issue to how Elements cached rangeproof-verification results. The cache could treat distinct transaction data as already verified, allowing an invalid transaction to pass validation.
The attacker then used Liquid’s standard peg-out process through SideSwap to obtain Bitcoin. Blockstream’s assessment says the exploit involved a vulnerability in the rangeproof-verification cache; the flaw was addressed in Elements v23.3.4, which used length-prefixed serialization for cache inputs.
Liquid’s incident report said the Federation reserve held about 4,205 BTC before the incident and fell to 197 BTC after the withdrawals and other peg-outs processed before operations halted. The attacker returned 3,400 BTC on September 7. In its September 8 update, the Federation said about 598.5 BTC remained outstanding at that stage.
Swaps returned before direct peg-outs
Blockstream released Elements v23.3.4 to address the vulnerability, and Liquid resumed network transactions in stages. Transactions restarted on September 10 while peg-outs remained disabled. By October 20, the Federation said semi-automated BTC-to-LBTC swaps were being enabled with participating providers, while direct Federation peg-outs remained restricted under additional safeguards.
The staged recovery separated access to swaps from the network’s own withdrawal process. The Federation’s October update described full 1:1 backing as a step before controlled reactivation of direct peg-outs for authorized key holders. The new announcement confirms the reserve condition has been met, but gives no date for that next step.
Full reserves do not settle every recovery question
Restored backing addresses the shortfall that left LBTC undercollateralized after the exploit. It does not, by itself, establish that all withdrawal controls have been lifted or that direct redemptions are available to users. The Federation’s statement points to swaps through providers as an existing route between Bitcoin and Liquid, while leaving the status of regular peg-outs unstated.
The distinction matters because reserve coverage and redemption access are separate parts of the recovery. Users can check the reported backing through Liquid’s public dashboard, but the Federation has not said in this update when authorized direct peg-outs will return. Its October recovery update said peg-out reactivation would follow the restoration of full 1:1 backing and remain subject to security and operational requirements.
Sources
- Original source Liquid Telegram channel t.me
Other pages read
- Blockstream, Liquid Network blog blog.liquid.net
- Liquid Federation, Liquid Network blog blog.liquid.net
Related stories
- Bitcoin Core discloses mining, Tor and block-processing flaws
- Preprint proposes journal-ordered withdrawal permits for Bitcoin custody
- bitcoinjs-lib Fixes Two PSBT Bugs That Hid Miner Fees
- XCM Incident Led to an Estimated Loss of Approximately $1.381 Million in DOT Value, Review Reports
- Avalanche Safe’s $7.45M Drain Began With an Unclaimed Address