Bitcoin vs Liquid

Liquid is a Bitcoin sidechain, which means its Liquid BTC is verifiably pegged 1:1 with Bitcoin, but the Liquid chain provides a number of enhancements. If you already understand Bitcoin, this page will help you map that knowledge onto Liquid quickly.

The relationship

Liquid is a layer 2 solution built on top of Bitcoin. It runs as a separate blockchain but is pegged to Bitcoin through a 1:1 two way peg. For every bitcoin locked on the main chain, an equivalent amount of LBTC is minted on Liquid. When you peg back out, the LBTC is destroyed and the equivalent bitcoin is released.

This means Liquid is not a competitor to Bitcoin. It's an extension that adds features Bitcoin doesn't natively have (confidentiality, fast blocks, native multi-asset) while still being fully backed by Bitcoin.

Side by side comparison

Property	Bitcoin	Liquid
Type	Layer 1 blockchain	Layer 2 sidechain of Bitcoin
Consensus	Proof of Work (mining)	Federated block signing (Strong Federation)
Block time	~10 minutes	~1 minute
Finality	Probabilistic (~6 confirmations recommended)	Fast, effectively final after 2 confirmations
Native currency	BTC	LBTC (1:1 pegged to BTC)
Privacy	Transparent (all amounts public)	Confidential Transactions by default
Asset support	BTC only	LBTC + any issued asset (multi-asset native)
Smart contracts	Bitcoin Script	Extended opcodes, Simplicity support
Network operators	Anyone can mine	Federation of functionaries
Fees	Variable, can spike	Consistently low (~0.1 sat/vB typical)
Reorg risk	Possible (deep reorgs rare but exist)	None (only 1 block reorgs are possible)

Note that although technically possible, Liquid has never had a reorg.

Consensus model

Bitcoin uses Proof of Work: miners compete to produce blocks, and security comes from the economic cost of attacking the network. Anyone can participate in mining.

Liquid uses a Strong Federation: a fixed but upgradeable group of 15 functionaries (exchanges, financial institutions, infrastructure companies) collectively produce blocks. Each block must be signed by at least two 11 out of 15 of the functionaries. This is faster and more predictable than Proof of Work, at the cost of having a known set of operators.

For finality:

Bitcoin: a transaction becomes harder to reverse with each new block. Most exchanges wait 3 to 6 confirmations.
Liquid: block signers will never reorganize beyond one block. Once a transaction has 2 confirmations (~2 minutes), it's effectively final.

The peg

Liquid's 2-way peg connects the two networks:

Peg in moves BTC to Liquid. You lock BTC in a federation controlled address, wait 102 Bitcoin confirmations (~17 hours), and receive the equivalent amount of LBTC on Liquid.
Peg out moves LBTC back to Bitcoin. You burn LBTC on Liquid, and the federation releases BTC on the main chain after ~17 minutes (via the Peg out Authorization Key, PAK, system).

The 102 confirmation requirement on peg-in exists to protect against deep reorganizations on Bitcoin. Peg-out uses PAK to ensure only authorized users can withdraw.

Privacy

Bitcoin transactions are fully transparent. Anyone can see which addresses sent how much to which addresses. This makes on-chain analysis tractable.

Liquid transactions use Confidential Transactions by default. Amounts and asset types are cryptographically blinded. Only the sender, receiver, or a third-party holding the blinding key can see what was transferred. See Confidential Transactions for the deep dive.

Assets

Bitcoin supports only BTC. Any token like functionality (Ordinals, Runes, BRC-20, etc.) is built as a convention on top of the protocol, not natively supported.

Liquid supports native multi-asset capability. Any participant can issue a new asset, and it becomes a first class citizen of the network. Transactions can move multiple asset types in a single operation. All assets share the same confidentiality guarantees.

Common Liquid assets include:

LBTC: the native currency, pegged to BTC
USDt: Tether's USD stablecoin on Liquid
Securities: tokenized bonds, stocks, and funds (typically via AMP2)
Custom tokens: any issuer can create their own

Fees

Bitcoin fees depend on demand for block space. They can spike dramatically during congestion (sometimes $50+ per transaction). Liquid fees are paid in LBTC and are consistently low, typically just a few cents. This makes Liquid practical for operations where Bitcoin fees would be prohibitive.

When to use Bitcoin vs Liquid

Use case	Better choice
Cold storage, long term holding	Bitcoin (maximum security, highest liquidity)
Fast settlement between counterparties	Liquid (1 min blocks)
Private transfers	Liquid (Confidential Transactions)
Issuing a new asset (stablecoin, security)	Liquid (native asset support)
High frequency operations	Liquid (low, predictable fees)
Maximum decentralization	Bitcoin

For an exchange, the typical setup is: Bitcoin for deep cold storage and long term reserves, Liquid for user facing operations (fast deposits/withdrawals, stablecoins, securities).

Same tooling, extended

Because Liquid is built on the Elements codebase (a software fork of Bitcoin Core), the tools feel familiar:

elementsd is the Liquid daemon (analogous to bitcoind)
elements-cli is the command line client (analogous to bitcoin-cli)
Descriptors, HD wallets, PSBTs from Bitcoin carry over (PSBTs become PSETs on Liquid)

If you've built Bitcoin integrations before, Liquid will feel like a natural extension. See Running Your Elements Node for how to operate a full node.