Definition: Liquid Bitcoin (L-BTC), also written LBTC, is the native currency of the Liquid Network, a Bitcoin sidechain. It represents bitcoin moved from the Bitcoin mainchain to Liquid through a two-way peg. L-BTC is used to pay Liquid transaction fees; it is not BTC held directly on Bitcoin, and using it depends on Liquid’s own chain and peg mechanisms.1, 2
| Asset | Liquid Network’s native currency, commonly written L-BTC or LBTC |
|---|---|
| Peg design | One BTC is locked on Bitcoin for each L-BTC issued on Liquid under the two-way peg |
| Main use | Pays transaction fees and transfers value on the Liquid sidechain |
| Official resources | |
| Directories | Bitcoin Coins & Tokens · Bitcoin Technology & Infrastructure · Bitcoin Directory |
How L-BTC is created
A peg-in moves BTC from Bitcoin to Liquid. A user creates a peg-in address with Liquid software, sends BTC to the associated federation-controlled Bitcoin address, and later claims the corresponding L-BTC on Liquid. Current Liquid documentation says a peg-in needs 102 Bitcoin confirmations before it can be claimed. Anyone with a Liquid node can initiate this process, but the wait and technical steps make it different from sending BTC to an ordinary Bitcoin address.2, 3
The intended peg ratio is one-to-one: BTC is locked on the Bitcoin mainchain while L-BTC is issued on Liquid, and the peg-out process destroys L-BTC as BTC is released. This is a federated design rather than a Bitcoin consensus rule. The Liquid Federation operates the functionaries and multisignature wallet that manage the peg, so the sidechain’s validation, operational safeguards, and ability to exit all matter to L-BTC holders.1, 2, 4
Peg-ins and peg-outs
| Action | What happens | What users should know |
|---|---|---|
| Peg-in | BTC is sent to the federation-controlled peg address; after the confirmation requirement, L-BTC can be claimed on Liquid. | Expect the Bitcoin confirmation delay, network fees, and Liquid wallet requirements. |
| Peg-out | L-BTC is destroyed on Liquid and the federation releases the equivalent BTC to an authorized Bitcoin address. | Direct peg-outs are restricted to eligible federation participants; many users rely on a supported swap provider or exchange. |
The public cannot treat L-BTC as a bearer claim that automatically converts into mainchain BTC from any wallet. Blockstream’s documentation says only Federation members can perform direct peg-outs; ordinary users generally need a member, exchange, or swap service to handle the exit. Before acquiring L-BTC, users should check which exit route is available to them, its fees and limits, and the current operating status of the provider.3, 5
L-BTC and BTC compared
| Feature | BTC | L-BTC |
|---|---|---|
| Network | Bitcoin mainchain | Liquid sidechain |
| Transaction fees | Paid in BTC | Paid in L-BTC |
| Validation and settlement | Bitcoin nodes validate transactions under Bitcoin consensus; miners produce proof-of-work blocks. | Liquid nodes validate its separate rules; federation functionaries sign blocks and operate the BTC peg. |
| Main dependency | Bitcoin network and wallet support | Liquid network support and a functioning peg or supported conversion route |
Privacy, fees, and compatibility
Liquid uses Confidential Transactions to hide amounts and asset types from the public, while participants in a transaction can see the information needed to transact. This feature is provided by Liquid’s protocol, not by Bitcoin mainchain transactions. L-BTC therefore cannot be spent directly as BTC: users need a Liquid-compatible wallet, and a wallet that supports Bitcoin but not Liquid will not treat L-BTC as a Bitcoin balance.4
Liquid transaction fees are paid in L-BTC, so a wallet holding only issued assets still needs some native L-BTC for network fees. Fees and settlement may differ from Bitcoin mainchain fees and confirmation behavior. The networks have separate ledgers, fee markets, and security assumptions.1, 4
2026 security incident and recovery
On September 6, 2026, an exploit involving Elements’ rangeproof-verification cache caused Liquid nodes to accept a transaction that created roughly 4,000 L-BTC without matching BTC backing. The attacker used a normal peg-out route to withdraw roughly 4,000 BTC. Blockstream’s incident assessment says the corrected chain removed the invalid transactions and their descendants, and that no inflation from the incident remained on the current Liquid chain after recovery. The same report said approximately 602 BTC remained subject to recovery efforts at publication.5
Liquid resumed user transactions after the September chain recovery, but peg operations were restored in stages. On October 20, the Liquid Federation said BTC–L-BTC swaps were resuming through participating providers while direct Federation peg-outs remained restricted. Blockstream later reported that the Liquid peg and 1:1 backing had been restored as of November 2, following new safeguards and an independent security audit. That update establishes the reported backing status at that date; it does not confirm that every direct peg-out route or provider is available to every user today.6, 7
History
- October 10, 2018: Blockstream announced the Liquid Network’s public launch.8
- September 6, 2026: A validation-cache exploit created unbacked L-BTC, triggering a network halt and chain recovery.5
- October 20, 2026: The Federation announced a staged reopening of BTC–L-BTC swaps while direct peg-outs remained restricted.6
- November 2, 2026: Blockstream later reported that 1:1 backing had been restored after additional safeguards and an independent audit.7
Page updated: November 15, 2026.
Related Terms
Related Articles
- Crypto Bridges: How They Work and Key Risks
- Bitcoin as Collateral: Bank Loans, Mortgages, and DeFi Explained
- What Happens to Bitcoin When All 21 Million Are Mined?
- What Is Tokenomics — And Why It Determines Whether a Crypto Project Survives
See Also
Crypto Tools – A curated list by CryptoGloss
Sources
- Liquid Network. “Liquid Assets.” Liquid Documentation. Accessed November 15, 2026. https://docs.liquid.net/docs/liquid-assets.
- Liquid Network. “Peg-in and Peg-out.” Liquid Documentation. Accessed November 15, 2026. https://docs.liquid.net/docs/advanced-pegin-pegout.
- Blockstream. “What Is a Liquid Peg-in?” Blockstream Help Center. Accessed November 15, 2026. https://help.blockstream.com/liquid-network/faqs/what-is-a-liquid-peg-in.
- Liquid Network. “Technical Overview.” Liquid Documentation. Accessed November 15, 2026. https://docs.liquid.net/docs/technical-overview.
- Blockstream Team. “Liquid Network Security Incident Assessment.” Blockstream Blog, September 23, 2026. Accessed November 15, 2026. https://blog.blockstream.com/liquid-network-security-incident-assessment.
- Liquid Federation. “Liquid Network Staged Recovery Update.” The Liquid Blog, October 20, 2026. Accessed November 15, 2026. https://blog.liquid.net/liquid-network-staged-recovery-update/.
- Blockstream. “Blockstream Quarterly Update: Q3 2026.” Blockstream Blog, November 5, 2026. Accessed November 15, 2026. https://blog.blockstream.com/blockstream-quarterly-update-q3-2026/.
- Mow, Samson. “The Launch of the Liquid Network.” Blockstream Blog, October 10, 2018. Accessed November 15, 2026. https://blog.blockstream.com/en-liquid-launch.