Skip to main content

This site is for educational purposes only. Nothing here constitutes financial advice.

Topic 101 of 189

Liquid Network

How Liquid is a Bitcoin sidechain with faster settlement, confidential transactions, and asset issuance — and where it fits in the Bitcoin scaling ecosystem alongside Lightning.

Beginner
8 min readUpdated July 2026Block Clarity Hub Editorial Team

The basics

What Liquid Is

Liquid Network is a Bitcoin sidechain operated by Blockstream. Users move BTC from Bitcoin L1 to Liquid (creating L-BTC), where transactions confirm in ~1 minute (vs ~10 minutes on L1). Liquid supports confidential transactions (hidden amounts and asset types), asset issuance (custom tokens beyond BTC), and higher throughput than Bitcoin L1. Liquid launched 2018 and has been operating steadily. It's a different scaling approach than Lightning — federated rather than trust-minimised, but with different capability trade-offs.

The Federation Model

Liquid is secured by a federation of ~15 organisations (exchanges, custodians, Bitcoin businesses) who jointly run the network's consensus. This differs from Bitcoin's fully decentralised model — federation members can technically freeze funds or reverse transactions if a supermajority agrees. In practice this has never happened, but the theoretical possibility exists. The federation model enables features Bitcoin can't easily support (confidential transactions, asset issuance) at the cost of adding trust.

Confidential Transactions

Liquid's confidential transactions hide amounts; according to a July 2023 Blockstream post, the deployed protocol uses Borromean ring signatures for its range proofs rather than Bulletproofs. Two users transacting in L-BTC can hide the amount from network observers while the network verifies conservation (inputs = outputs). This is useful for exchanges wanting to hide large transfers, businesses wanting confidential settlements, and institutional traders wanting to hide flow information. Bitcoin L1 doesn't support confidential transactions; Liquid does. Whether this is worth the federation trade-off depends on the use case.

  • Bitcoin sidechain with 1-minute confirmations
  • Confidential transactions (hidden amounts) via Bulletproofs
  • Asset issuance beyond BTC
  • Federation of ~15 organisations vs Bitcoin's full decentralisation

Key Takeaways

  • Liquid is a Bitcoin sidechain operated by a federation
  • Confidential transactions enable amount privacy on-Liquid
  • Trade-off: federation trust vs additional capabilities
  • Different scaling approach than Lightning; different use cases

Going deeper

Peg-In and Peg-Out Mechanics

Moving BTC to Liquid (peg-in): user sends BTC to a special federation address; after confirmations, L-BTC appears on Liquid. Moving back (peg-out): more complex. User burns L-BTC and sends withdrawal request; federation members sign a Bitcoin transaction releasing BTC to user's address; peg-out completes after Bitcoin confirmations. Peg-outs are subject to federation availability; if federation members are offline or refuse, peg-out can be delayed. In normal operation, this happens smoothly and quickly. In edge cases (federation dispute, coordinated refusal), peg-out risk is real.

Asset Issuance and Tokenised Assets

Liquid supports issuing custom assets beyond L-BTC. Bitfinex has issued L-USDt (Tether on Liquid). Various tokenised securities exist on Liquid. The asset issuance model is simpler than Ethereum's ERC-20 (no general smart contracts) but sufficient for many use cases. Liquid assets can use Liquid's confidential transaction features — an issuer can issue tokens where amounts are hidden but network still validates conservation. This makes Liquid useful for institutional issuers wanting some privacy but not full anonymity.

Comparison to Rootstock

Rootstock (RSK) is another Bitcoin sidechain, focused on smart contracts rather than confidentiality. RSK is EVM-compatible; you can port Ethereum contracts to RSK. Different design bet: RSK adds programmability at cost of complexity; Liquid adds confidentiality and asset issuance while staying simpler. Both are federated. Both have modest adoption relative to Bitcoin L1. The choice between them depends on specific use case — programmable smart contracts (RSK) or confidential transactions and simple asset issuance (Liquid).

Liquid Adoption Reality

Liquid has meaningful adoption in specific niches — Bitfinex's L-USDt is a real product, various tokenised securities exist, some large Bitcoin businesses use it for confidential transfers. But mainstream Bitcoin users largely aren't aware of Liquid. It's more institutional infrastructure than retail product. Whether Liquid grows into broader adoption or stays niche institutional infrastructure is an open question.

Key Takeaways

  • Peg-in is straightforward; peg-out depends on federation cooperation
  • Asset issuance enables custom tokens on Liquid
  • L-USDt (Tether) is Liquid's most-used asset by volume
  • Rootstock is an alternative Bitcoin sidechain focused on smart contracts

Under the hood

Federation Governance

Liquid's federation makes decisions about protocol upgrades, member addition/removal, and emergency responses. The governance is coordinated by Blockstream but requires supermajority federation consent for major decisions. This is more centralised than Bitcoin but less centralised than a single-operator system. In practice, federation governance has been stable — no publicised major disputes. Whether this stability persists as federation composition evolves is uncertain. Reading Blockstream's governance publications gives current federation status.

Cryptographic Security Model

Liquid's security depends on federation members' key security. If federation members' HSMs (hardware security modules) are compromised, funds could theoretically be stolen. Each federation member operates independently; no single member can act unilaterally, but 11 of 15 (or similar threshold) could compromise the network. This is threshold cryptography protecting the network — meaningfully different from Bitcoin's PoW security. The trade-off: faster settlement, more features, but different trust model.

Liquid vs Lightning — Complementary or Competitive

Liquid and Lightning aren't directly competitive — they solve different problems. Lightning is trust-minimised, best for small frequent payments. Liquid is federated, best for larger transactions with confidentiality needs or asset issuance. Some users use both. Some businesses use Liquid for treasury and settlement, Lightning for customer payments. The Bitcoin scaling story is 'multiple layers with different trade-offs' rather than 'one winning approach.' Liquid's role is confidentiality-plus-assets; Lightning's is trust-minimised-payment.

Whether Liquid Stays Relevant

As Ethereum L2s mature and offer similar confidentiality (via ZK privacy) with programmable smart contracts, Liquid faces competitive pressure. Its advantages (Bitcoin-native, established federation, real production usage) matter for Bitcoin-specific use cases. Its disadvantages (federation model, less programmability, less community awareness) matter for broader adoption. Whether it grows or gradually fades depends on Bitcoin's ecosystem evolution. The federation seems committed to continued operation, so persistence is likely; growth trajectory is less clear.

Understanding Liquid Requires Understanding Trade-offs

Liquid's federation model is often criticised by Bitcoin purists as centralising Bitcoin. The response: it's an optional layer, not required for Bitcoin's core security. Users who want federation-free operation stay on Bitcoin L1 or Lightning; users who want Liquid's features accept the federation trade-off. This 'multiple layers for different needs' framing is more useful than absolutist judgments. Liquid is a tool with specific trade-offs; whether it fits your needs is context-dependent.

Key Takeaways

  • Federation governance requires supermajority for major decisions
  • Cryptographic security depends on HSM security and threshold cryptography
  • Complementary to Lightning; different use cases
  • Whether Liquid grows or gradually fades depends on Bitcoin ecosystem evolution
  • Trade-offs framing more useful than absolutist decentralisation judgments

Related Content

Zcash Architecture

How Zcash uses zk-SNARKs to enable optional shielded transactions, why Sapling was the breakthrough that made shielded pool usage practical, and how Halo2 removed the trusted setup.

Tornado Cash Mechanics and OFAC Context

How Tornado Cash's Merkle tree deposit-and-mix architecture worked, the August 2022 OFAC sanctions, the 2024 Van Loon ruling and the March 2025 delisting, and the broader question of sanctioning immutable smart contracts.

Aztec and Railway — Ethereum Privacy Layers

How Aztec's zkRollup and the RAILGUN shielded pool (used through the Railway wallet) approach privacy on Ethereum from different architectural angles, and what shipping ZK-based Ethereum privacy actually looks like.

Lightning Network — Deep Dive

How Lightning's payment channels enable instant Bitcoin transactions, the routing challenges that shape the network's topology, and why LN adoption has grown more slowly than early forecasts suggested.

Validium, Plasma, and State Channels

The scaling designs that lost to rollups — Validium (off-chain data), Plasma (mass exit games), and state channels (bilateral off-chain) — and why understanding them helps make sense of current rollup design.

App-Chains and Rollup-as-a-Service

How Cosmos-style app-chains and modern Rollup-as-a-Service (RaaS) providers (Caldera, Conduit, AltLayer, Gelato) let applications deploy dedicated chains, and the trade-offs vs shared chains.

Cosmos IBC and Interchain Security

How Cosmos IBC enables cross-chain messaging without wrapped assets, how Interchain Security (ICS) let chains rent security from the Cosmos Hub before the Hub removed it in 2026, and what these primitives mean for Cosmos's app-chain thesis.

Polkadot Parachains

How Polkadot's parachain model works — shared security via the Relay Chain, XCM cross-chain messaging, agile coretime — and how the network has evolved from parachain auctions to coretime markets.

References & further reading