Glossary

Liquid Network

A federated Bitcoin sidechain by Blockstream offering confidential transactions, faster settlement, and issued assets for traders and institutions.

Key Takeaways

  • The Liquid Network is a federated sidechain built on Bitcoin that enables 1-minute block times, confidential transactions, and native asset issuance for traders, institutions, and exchanges.
  • Security relies on a federation of 15 functionaries using an 11-of-15 multisig threshold stored in HSMs, making it a trust-minimized but not trustless system compared to Layer 2 protocols like Lightning or Spark.
  • Liquid supports issued assets including L-BTC, Tether USDt, tokenized securities, and fiat-pegged stablecoins, positioning it as infrastructure for Bitcoin-native financial products rather than everyday payments.

What Is the Liquid Network?

The Liquid Network is a federated Bitcoin sidechain developed by Blockstream and operated by a globally distributed federation of cryptocurrency companies. Launched in October 2018 as Bitcoin's first production sidechain, Liquid enables faster settlement, private transactions, and the issuance of digital assets on a blockchain that is anchored to Bitcoin through a two-way peg mechanism.

Liquid targets a different audience than payment-focused protocols like the Lightning Network. Where Lightning optimizes for instant micropayments, Liquid serves traders moving funds between exchanges, institutions settling large transactions privately, and issuers creating tokenized assets like stablecoins and securities. The network has grown to over 87 federation members across six continents, with more than $3.2 billion in total value locked as of early 2026.

Technically, Liquid is built on Elements, an open-source sidechain platform based on the Bitcoin codebase. Elements extends Bitcoin with confidential transactions, native asset issuance, Segregated Witness, and a federated consensus model called Strong Federations.

How It Works

Liquid replaces Bitcoin's proof-of-work consensus with a federated signing model. Instead of miners competing to produce blocks, 15 functionaries take turns proposing blocks in a round-robin schedule. Each block requires 11-of-15 signatures to be valid.

The Federation Model

The Liquid federation consists of two roles that functionaries perform:

  • Block signers: propose and co-sign new Liquid blocks every 60 seconds, requiring 11-of-15 agreement for each block
  • Watchmen: manage the Bitcoin-side multisig wallet that holds the pegged BTC, processing peg-out requests and guarding funds

Each functionary stores its signing key in a dedicated hardware security module (HSM), distributed across different jurisdictions globally. The network can tolerate up to 4 functionaries going offline while continuing to operate. If 5 or more become unavailable (breaking the two-thirds quorum), the blockchain freezes until enough functionaries come back online.

As an emergency fallback, 2-of-3 backup recovery keys are held by Blockstream in geographically distributed cold storage. These keys become accessible only after a timelock of 4,032 Liquid blocks (approximately 28 days) per UTXO. During normal operation, the timelocks refresh every 1,008 blocks (roughly 7 days), preventing accidental activation.

The Peg Mechanism

Liquid uses a federated two-way peg to move Bitcoin between the main chain and the sidechain. The pegged asset, L-BTC, is verifiably backed 1:1 by BTC held in the federation's multisig wallet.

Peg-in (BTC to L-BTC):

  1. The user sends BTC to a federation-controlled address generated by their Liquid wallet software
  2. The transaction requires 102 confirmations on Bitcoin (approximately 17 hours) as a security measure against deep chain reorganizations
  3. Once confirmed, the user creates a peg-in claim transaction on Liquid to receive the equivalent L-BTC

Peg-out (L-BTC to BTC):

  1. The user submits a peg-out request on the Liquid Network
  2. Watchmen verify the request using Peg-out Authorization Keys (PAKs) to ensure BTC is only sent to authorized addresses
  3. Watchmen batch and process peg-outs, typically completing within 11 to 35 minutes depending on network conditions
# Peg-in: send BTC to the federation address
elements-cli getpeginaddress
# Returns: mainchain_address, claim_script

# After 102 Bitcoin confirmations, claim L-BTC
elements-cli claimpegin <raw_btc_tx> <txout_proof> <claim_script>

# Peg-out: convert L-BTC back to BTC
elements-cli sendtomainchain <btc_address> <amount>

Confidential Transactions

All Liquid transactions hide both amounts and asset types by default using cryptographic blinding. This is implemented through three primitives:

  • Pedersen commitments: homomorphic commitments that conceal transaction amounts while allowing validators to verify that inputs equal outputs (preventing inflation)
  • Range proofs: zero-knowledge proofs confirming that hidden amounts fall within a valid range (non-negative, up to 2^52 satoshis) without revealing the actual value
  • Asset surjection proofs: cryptographic proofs ensuring every output asset type matches some input asset type, preventing counterfeit asset creation while hiding which specific assets flow where

Only the sender and recipient hold unblinding keys. They can selectively share these with third parties like auditors or regulators for disclosure. The tradeoff is that confidential transactions are larger than standard Bitcoin transactions, which accelerates blockchain growth on the sidechain.

Issued Assets

Unlike Bitcoin's base layer, Liquid supports native asset issuance directly at the protocol level. Any federation member or user can issue tokens that inherit Liquid's confidential transaction properties. Notable assets on the network include:

  • L-BTC: Liquid Bitcoin, the native peg asset backed 1:1 by BTC in the federation wallet, publicly auditable on-chain
  • Tether USDt: the world's largest stablecoin is issued natively on Liquid, enabling private and fast stablecoin transfers
  • DePix: a BRL-denominated stablecoin pegged to the Brazilian Real, powering remittance and merchant payments across Brazil and accounting for a significant share of Liquid's transaction volume
  • Tokenized securities: platforms like STOKR have issued equity, debt, and hashrate-backed instruments on Liquid, with over $1.5 billion in tokenized asset volume by 2025

The network recorded over 18,000 new asset issuances in Q1 2026 alone, reflecting growing adoption for tokenized financial products. For a deeper look at how sidechains like Liquid compare to other Bitcoin scaling approaches, see the Liquid Network deep dive and the Bitcoin Layer 2 comparison.

Use Cases

Inter-Exchange Settlement

Liquid's original use case: traders moving funds between exchanges without waiting for Bitcoin's 6-confirmation standard (roughly 60 minutes). With 2-minute finality and confidential transactions hiding trade sizes, Liquid lets traders rebalance positions across venues quickly and privately.

Private Large-Value Transfers

Institutions and high-net-worth individuals use Liquid for large transactions where privacy matters. On Bitcoin's base layer, every amount is publicly visible. On Liquid, amounts and asset types are blinded by default, visible only to the transacting parties and anyone they choose to share unblinding keys with.

Stablecoin and Token Issuance

Liquid provides a Bitcoin-anchored platform for issuing stablecoins, security tokens, and other digital assets. Because Liquid inherits Bitcoin's UTXO model and scripting capabilities (with extensions), issuers can create regulated financial instruments without depending on Ethereum or other smart contract platforms.

Liquid vs. Lightning vs. Spark

Each Bitcoin scaling approach optimizes for different use cases. Liquid serves traders and institutions needing confidential settlement and asset issuance. The Lightning Network handles high-frequency retail payments with near-instant settlement and no federation trust. Protocols like Spark combine self-custodial security with stablecoin support and Lightning interoperability, targeting the payment and wallet infrastructure layer.

AspectLiquidLightning
ArchitectureFederated sidechainPayment channel network
Trust modelFederated (11-of-15)Trustless (cryptographic)
Settlement~2 minutesNear-instant
PrivacyConfidential by defaultLimited (onion routing)
Asset issuanceNative supportNot supported
Best forTrading, institutions, tokensRetail payments, micropayments

Risks and Considerations

Federation Trust

Liquid's security model requires trusting that fewer than 11 of the 15 functionaries will collude. While each key is stored in a separate HSM across different jurisdictions, the system is fundamentally federated, not trustless. A coordinated attack compromising 11 HSM devices could theoretically steal the pegged BTC. This contrasts with Layer 2 solutions like Lightning and Spark, where users retain self-custody of their funds with cryptographic enforcement.

Peg-In Latency

The 102-confirmation requirement for peg-ins means approximately 17 hours of waiting to move BTC onto Liquid. This protects against deep chain reorganizations but creates significant friction for users who need funds quickly. Peg-outs are faster (11 to 35 minutes) but still slower than native Lightning payments.

Confidential Transaction Size

The cryptographic proofs required for confidential transactions (range proofs and surjection proofs) make Liquid transactions significantly larger than standard Bitcoin transactions. This increases storage requirements and can affect fee calculations, though Liquid's lower block demand generally keeps fees minimal.

Centralization Concerns

Blockstream holds the 2-of-3 emergency recovery keys and leads Liquid development. While plans exist to transfer emergency key control to the federation itself through DynaFed upgrades, the current arrangement concentrates fallback authority. The identities of the 15 functionary operators are also not fully public, limiting external auditability of the federation's decentralization.

Limited Programmability

While Liquid extends Bitcoin Script with additional opcodes, its smart contract capabilities are more limited than platforms like Ethereum. Blockstream has been deploying Simplicity (a new smart contract language) on Liquid, including post-quantum signature verification as of early 2026, but the ecosystem of applications remains smaller than competing platforms.

This glossary entry is for informational purposes only and does not constitute financial or investment advice. Always do your own research before using any protocol or technology.