A gold Bitcoin coin on a dark background resting on a glass platform with one corner still unfinished, while a thin stream of gold light flows toward the gap
Original AI-generated illustration; not real data.

Liquid's Exit to Bitcoin Is Open Again. Here's What L-BTC Holders Can Do While the Reserve Is 602 BTC Short

NodeWitness Team 8 min read

For the first time since September 6, there is a practical way to turn L-BTC back into bitcoin. The backing hasn't caught up yet: the Federation's reserve covers 85.77% of the L-BTC in circulation. About 600 BTC have been promised "in the coming days," and you don't have to take anyone's word for when they land.

If you've held L-BTC through the last six weeks, today changes your options more than it changes the numbers. At 12:49 UTC on October 20, the Liquid Federation said BTC↔L-BTC swaps are being enabled with participating providers, "without protocol-imposed volume limits" [1][2]. The Federation's own peg-outs are a separate matter. They stay restricted until the reserve is back to full 1:1 backing [1].

Within the hour, Samson Mow, CEO of JAN3, the company behind the AQUA wallet [9], posted that the external security audit is complete and that "the ~600 BTC shortfall will be added to the Federation wallet in the coming days" [3]. That is a specific, checkable claim. Most of this piece is about how to check it.

How the reserve got here

Blockstream's incident assessment lays out the sequence [6]. On September 6 at 13:53 UTC, an attacker exploited a flaw in Elements' rangeproof verification cache, and Liquid accepted a transaction that created roughly 4,000 L-BTC with nothing behind it. Those tokens were redeemed through SideSwap's peg-out service, and the Federation released 3,996.02 BTC on Bitcoin. The reserve fell from about 4,205 BTC to 197 BTC. The attacker returned 3,400 BTC the next day, leaving about 602 BTC outstanding.

The fix shipped in Elements v23.3.4 on September 9, and transactions inside Liquid resumed on September 10 [6]. What didn't come back was a reliable road out to the main chain.

The numbers as of this afternoon

Mempool's Liquid explorer tracks the Federation's coins on Bitcoin and the L-BTC supply on Liquid, and puts them side by side [7]. Its public API returned the following at 16:59 UTC on October 20:

Figure Value
L-BTC in circulation (Liquid block 4,109,107) 4,234.76 L-BTC
BTC held by the Federation (Bitcoin block 972,354) 3,632.23 BTC
Shortfall 602.53 BTC
Coverage 85.77%

At $82,646 per bitcoin, mempool.space's price at 16:55 UTC, the shortfall is worth about $50 million [7]. The circulating figure reconciles with the asset's own lifetime totals: 18,387.58 BTC pegged in, minus 14,142.80 pegged out, minus 10.03 burned [7].

If you hold L-BTC: your options today

Swap out through SideSwap. As of October 20, SideSwap again pays out bitcoin for L-BTC at 1:1, minus its standard 0.1% fee [4]. The plumbing behind it is different for now. Because Federation peg-outs are still off, every payout comes from SideSwap's own Bitcoin wallet, and the L-BTC it collects is swapped for bitcoin in bulk under the arrangement Liquid described [4]. You receive the same thing, bitcoin at your address, but throughput depends on SideSwap's inventory.

Swap out from AQUA. At 13:34 UTC, AQUA said the SideSwap integration inside its app is "back to normal," with 1:1 L-BTC to BTC peg-outs [5]. SideSwap notes that a wallet using its service may charge a fee of its own [4].

Go out over Lightning. AQUA's Indra swap fees are back to 0.25%, and rate limits are being relaxed [5]. The reverse direction, Lightning into Liquid, isn't restored yet; AQUA says it is coming "as soon as possible" [5].

Wait. That is a legitimate choice. L-BTC works normally inside Liquid, and the Federation says the final stage is restoring full 1:1 backing [1]. Until it does, each L-BTC is backed by about 0.86 BTC, and no one has said publicly what happens if the shortfall is never filled.

Risks worth keeping in view:

  • Liquidity, not protocol, is the bottleneck. If many holders head for the exit at once, provider inventory sets the pace. Send a small amount first, then the rest.
  • Fake "recovery" services. Incidents like this draw sites and accounts offering to "unlock" or "recover" L-BTC. No legitimate exit needs your seed phrase, the same rule that applied to the BLAKE2b and eCash fork balances.
  • Never send BTC straight to the Federation address. It's printed in explorers and in articles, including this one. Sending to it does not mint you any L-BTC; the coins are simply lost to you. Getting onto Liquid takes a peg-in address generated for you, or a provider.
  • Pegging in today means buying into the gap. SideSwap has accepted peg-ins since September 11 [4]. Until the shortfall is filled, new L-BTC carries the same 85.77% backing as the old.

How to verify the 602 BTC on-chain

The claim is that roughly 600 BTC will be added to the Federation wallet [3]. Seeing bitcoin arrive isn't enough to confirm it. You need two numbers moving the right way.

1. Track the gap, not the balance. The reserve moves every day with normal peg-ins and peg-outs. A user pegging in 10 BTC adds 10 BTC to the reserve and also mints 10 L-BTC, so the gap doesn't move. The shortfall closes only when about 602 BTC enter the reserve without a matching rise in L-BTC supply. (It could, in principle, also close the other way, with L-BTC being burned. Mow's post points to a deposit.)

2. Watch the main Federation address. The reserve sits in 111 coins across 16 addresses (112 on-chain if you count a 9,737-satoshi dust output the explorer leaves out), but 99% of it is in one: bc1qdlld6antmv4xug242ed83q7k4rqw50cwfns38szx4qu2f4jwaxxsuhwxxr, holding 3,601.47 BTC [7]. It's the address that received the attacker's 3,400 BTC return on September 7, in block 965,950 [8]. That makes it the likeliest destination for the 602 BTC, though the Federation hasn't said so.

3. Confirm the address belongs to the Federation yourself. You don't have to trust the explorer's label. Every time the Federation spends from that address, the spending transaction reveals the script that locks it, the same way an ordinary spend puts an address's public key on display. Hash that script and it matches the address, which any node can check. The script requires 11 of the Federation's 15 signers. A coin that sits unmoved for 8,064 blocks, about eight weeks, also becomes spendable by 2 of 3 emergency keys [8], which is why the Federation refreshes its coins regularly. Right now no reserve coin has passed that deadline [7].

4. Ignore the dust. Anyone can send a few satoshis to a well-known address, and people do. What matters is one deposit, or a handful, adding up to roughly 602 BTC.

5. Then watch for the peg-out switch. Once the gap reads zero on-chain, the next step is the Federation reopening its own peg-outs. SideSwap has said it will publish a note with that day's liquid.network figures [4].

We've rerun the reserve side of this on our own Bitcoin node instead of leaning on the explorer. At block 972,341 (14:56 UTC on October 20), the main address held 3,601.47 BTC, and the 111 coins the explorer counts were all unspent, totaling 3,632.23 BTC, the same figure as in the table. The 3,400 BTC return still sits untouched at that address, and the 11-of-15 script hashes to it [8]. No reserve coin has reached the emergency-key deadline yet; the oldest has been sitting for 6,391 of the 8,064 blocks. What our node can't check is the L-BTC supply, which lives on the Liquid chain, so that figure comes from mempool [7]. If the 602 BTC show up, we'll cover it in a new piece with the block and the transaction.

The whole story fits in one subtraction: L-BTC in circulation minus BTC in reserve. Today it's 602.53. When it reads zero, Liquid is back at 1:1.

Sources

Source type in parentheses. Times in UTC.

  1. Liquid Federation, Liquid Network Staged Recovery Update, October 20, 2026. Swaps with participating providers, Federation peg-outs restricted until 1:1, reserve monitoring through block explorers. (Primary, official statement)
  2. Liquid Network, Liquid Network Restoration Update, October 20, 2026, 12:49. (Primary, official X account)
  3. Samson Mow, post on X, October 20, 2026, 13:28. Audit complete; ~600 BTC "in the coming days." (Primary, statement on X)
  4. SideSwap, Peg-out is open again on SideSwap, October 20, 2026, and Peg-ins are open again on SideSwap, September 11, 2026. 0.1% fee, payouts from its own wallet, bulk swaps, third-party wallet fees. (Primary, provider)
  5. AQUA, update on X and note on reverse swaps, October 20, 2026, 13:34. (Primary, provider)
  6. Blockstream, Liquid Network Security Incident Assessment, September 23, 2026 (republished on the Liquid blog on September 25). Exploit mechanics, amounts released, reserve before and after, 3,400 BTC returned and ~602 BTC outstanding. (Primary, technical report)
  7. mempool, Liquid Federation Holdings and its public API, read on October 20, 2026, at 16:59 UTC (Liquid block 4,109,107; Bitcoin block 972,354), with mempool.space pricing at 16:55 UTC. Circulating L-BTC, reserve, addresses, coins and expired timelocks. (Secondary, open-source on-chain explorer)
  8. Bitcoin transactions: 3,400 BTC return (block 965,950) and a Federation spend revealing the 11-of-15 script (block 972,279; both of its inputs from the main address reveal the same script). Verified on our own node (a full Bitcoin Core 31.1.0 node and its indexing service) at block 972,341, October 20, 2026, 14:56 UTC, along with the main address balance and the 111 reserve coins. (Primary, chain data)
  9. Samson Mow, X profile, read on October 20, 2026: "CEO @JAN3com, building @AquaBitcoin." (Primary, own profile)

More in Network and mining

See all 15 articles in Network and mining →

Last updated: October 20, 2026