Liquid Network recovery is back in focus after reports highlighted Samson Mow’s statement that roughly 600 BTC would be added to the Federation’s reserves “in the coming days.” For L-BTC holders, the issue is whether the funding will restore full backing and clear the way for normal Bitcoin redemptions.
The headline needs a timing distinction. October 27 coverage repeated the commitment, but a publicly accessible reproduction of Mow’s statement is dated October 20. It should therefore be treated as an existing recovery pledge receiving renewed attention, rather than a newly verified completion announcement.
Mow is the CEO of JAN3. The statement attributed to him should also be distinguished from the Liquid Federation’s own published recovery instructions.
Liquid Network Recovery: What Has Been Confirmed?
The Federation’s October 20 recovery update describes software changes for managing Bitcoin reserves and a phased return of services.
It says participating providers are enabling semi-automated BTC–L-BTC swaps while direct Federation peg-outs remain restricted. Restoring full 1:1 backing comes before the controlled reactivation of those peg-outs for authorized participants, with remaining security and operational requirements also needing completion.
Recovery milestone | What the reviewed disclosures establish |
|---|---|
Network transactions | Liquid reported their resumption on September 10 |
Provider-assisted swaps | Enabled as part of the October 20 recovery stage |
Remaining reserve gap | Roughly 600 BTC in subsequent reporting |
Funding timeline | Mow said the gap would be filled “in the coming days” |
Normal Federation peg-outs | Restricted in the latest official recovery update reviewed |
These are separate milestones. A working transfer service does not, by itself, prove that the reserve shortfall has disappeared.
The Original Exploit Was Larger Than 600 BTC
Blockstream’s incident assessment traces the September 6 exploit to a vulnerability in Elements’ rangeproof verification cache.
In plain terms, the software accepted a transaction that created approximately 4,000 L-BTC without matching Bitcoin backing. Those tokens were subsequently used to withdraw Bitcoin through the peg-out process via SideSwap.
The report says 3,400 BTC was returned on September 7, leaving approximately 602 BTC outstanding at the time of that assessment. Later coverage rounds the remaining gap to about 600 BTC.
That makes “600 BTC hack” an incomplete description. The figure refers to the unresolved balance following a much larger incident.
Blockstream’s assessment also identifies a weakness in a member’s peg-out configuration alongside the software vulnerabilities. It says no private keys were compromised, illustrating that protecting signing keys alone was insufficient to prevent this loss.
Why Swaps and Peg-Outs Are Different
Liquid is a federated Bitcoin sidechain. Its intended design matches L-BTC with Bitcoin held in the reserve, allowing value to move between the two networks.
A direct peg-out uses the Federation’s mechanism to release Bitcoin against a Liquid-side transaction. A swap provider instead offers a conversion service under its own operating conditions.
For a holder, both may provide a route from L-BTC to BTC. Operationally, however, they are different arrangements. A provider offering swaps does not establish that the normal Federation redemption process has reopened.
This distinction also appears in broader asset-backed markets. Bitnxt’s coverage of GoldZip’s cross-chain gold integration examined why moving a token and redeeming its underlying backing require separate scrutiny.
What the Reported Reserve Transfer Does—and Does Not—Show
October 27 reporting described a transfer of approximately 2.53 BTC to the Federation wallet, characterizing it as a test. The same coverage put reserves near 3,649 BTC against roughly 4,249 L-BTC, implying about 85.9% coverage.
Those are reported figures, not a live reserve audit independently completed by Bitnxt. They should not be presented as an exact balance for October 28.
Even if confirmed, a small test transfer would establish only that a particular amount arrived. It would not demonstrate that hundreds of additional BTC had been deposited.
The next decisive evidence would be a reconciled reserve update, supported by verifiable transactions, and a formal notice specifying which redemption functions have resumed.
Bitnxt View: Recovery Must Be Measured at the Exit
Our view is that the funding commitment is meaningful, but holders need observable results: sufficient reserves and a dependable way to redeem.
Bitnxt’s earlier reporting on Solana’s delivery-versus-payment infrastructure explored a related principle—successful settlement depends on the complete transaction, not just one functioning component.
Liquid presents a different technical problem, but the same practical question applies: can the holder complete the intended exchange and receive the underlying asset?
Restoring the missing Bitcoin would address the financial gap. Durable confidence also requires clear accounting, effective controls and evidence that the repaired system works under normal operating conditions.
The recovery story remains open until those outcomes are demonstrated. “Will be covered” is a commitment worth tracking; it is not interchangeable with “fully restored.”
