What is the Liquid Network?
👋 New to this? Just start reading at the top — it begins in plain English and gets more detailed as you scroll. Jump to any level:
🟢 The simple version
Plain English — no jargon. Start here.
The Liquid Network is a federated Bitcoin sidechain operated by Blockstream and a consortium of exchanges and institutions — providing faster, more confidential Bitcoin transactions between members through a 2-way peg where BTC is locked on Bitcoin mainchain and released as L-BTC on the Liquid Network.
What Liquid solves — exchange settlement
Bitcoin's 10-minute block time creates friction for exchanges that need to move large amounts of BTC quickly. An exchange wanting to settle a large BTC transfer to another exchange must wait for multiple Bitcoin confirmations (typically 6, taking ~60 minutes) before the transaction is considered final. During high-network-fee periods, this settlement also becomes expensive.
Liquid was designed specifically for this inter-exchange settlement use case. Liquid blocks are produced every 2 minutes (vs Bitcoin's ~10 minutes), with strong finality after 2 blocks (~4 minutes). Transaction fees are low and predictable. Confidential Transactions hide amounts from external observers, protecting trading strategies during large settlements.
The federation model
Unlike Bitcoin (miners) or proof-of-stake chains (stakers), Liquid is secured by a federation of "functionaries" — approximately 15 trusted institutions, primarily cryptocurrency exchanges and Bitcoin businesses (including Bitfinex, Kraken, Coinbase Custody, and others). The federation collectively manages the 2-way peg and block production. This is a trusted model — Liquid's security depends on the honesty of the federation members. The trade-off for this trust: speed, privacy, and asset issuance features beyond what trustless systems currently provide.
Liquid Assets — tokenisation on Liquid
Liquid supports the issuance of custom assets — security tokens, stablecoins, and any tokenised asset — that benefit from Liquid's confidential transaction model. Tether (USDT) has issued on Liquid. Several exchanges have issued exchange tokens on Liquid. Asset issuance on Liquid inherits Confidential Transactions — the amount of an asset transfer is hidden from outside observers.
Is it legal in India?
Yes. L-BTC is a VDA under Indian law. 30% tax and 1% TDS apply. See India regulation.
🟡 A bit more detail
For when you want to go a little deeper.
Confidential Transactions on Liquid
Liquid implements Confidential Transactions (CT) — a cryptographic protocol that hides transaction amounts from external blockchain observers while still allowing the network to verify that no coins are created or destroyed. CT uses Pedersen commitments (the same construction as MimbleWimble) — amounts are committed to a value that hides the actual number while allowing verification that inputs equal outputs. Range proofs prove the committed values are positive without revealing them. On Liquid, CT is the default for L-BTC and Liquid Asset transfers — unlike Zcash where shielding is optional.
Liquid is used by cryptocurrency exchanges for inter-exchange settlement of large BTC transfers. The most common use: exchange A holds BTC for a large client and needs to transfer it to exchange B quickly and confidentially. Liquid provides ~4 minute finality (vs ~60 minutes on Bitcoin mainchain), transaction amounts hidden from public blockchain analysis, and low predictable fees. Stablecoins on Liquid (USDt, others) allow trading between Liquid members without leaving the Liquid sidechain. Several derivatives exchanges use Liquid for collateral movement.
The Liquid peg: BTC ↔ L-BTC
Pegging in: a user sends BTC to a peg-in address (a Bitcoin multisig controlled by the Liquid federation). After 102 Bitcoin confirmations (~17 hours), the equivalent L-BTC is released on Liquid — the long confirmation requirement protects against Bitcoin reorganisations. Pegging out: a user sends L-BTC to a peg-out transaction on Liquid; after 2 Liquid confirmations, the federation releases the corresponding BTC on mainchain. The asymmetric wait times (peg-in is slow, peg-out is fast) reflect Bitcoin's slower finality vs Liquid's faster finality.
Key Liquid metrics: L-BTC in circulation (total peg-in), Liquid Asset issuance count, federation member count, and transaction volume. The trust model is Liquid's primary limitation — users must trust the ~15 federation members. If a supermajority of functionaries collude, they could theoretically confiscate pegged BTC. The exchange use case is well-served by this model (exchanges are regulated entities with reputational incentives to behave correctly), but it is not suitable for trustless applications. Live data: Blockstream Liquid Explorer.
🟣 The full technical picture
For the technically curious.
Liquid's Elements framework
Liquid is built on Elements — Blockstream's open-source framework for building federated Bitcoin sidechains. Elements extends Bitcoin's codebase with Confidential Transactions, Confidential Assets (amounts and asset types hidden), and custom federation-based block signing. Any organisation can use Elements to build their own private federated sidechain. Liquid is the first and largest public deployment of Elements.
Source: Blockstream documentation. docs.liquid.net · Elements: elementsproject.org
Confidential Assets — hidden asset types
Liquid extends Confidential Transactions to Confidential Assets — not only are transaction amounts hidden, but the type of asset being transferred is also hidden from external observers. An external blockchain analyst sees only that a transaction occurred between two addresses, not whether it was L-BTC, USDT, or a security token. This confidential asset model is cryptographically achieved by including the asset type in the Pedersen commitment alongside the amount — an asset generator G_asset replaces the standard generator, blinding the asset type from observers who do not know the asset generator.
Liquid's block signing uses a threshold signature scheme among the ~15 federation functionaries. Each functionary runs a Hardware Security Module (HSM) — similar to Rootstock's Powpeg — that holds the signing key and is programmed to only sign a block that follows consensus rules. The threshold is typically 11 of 15 signers — a block is invalid if fewer than 11 functionaries sign it. This threshold ensures resilience against up to 4 functionary failures or compromises simultaneously. The HSMs use a round-based protocol where functionaries propose and vote on the next block in a Byzantine fault-tolerant consensus round, completing in seconds rather than minutes.
Key facts
- Type: Federated Bitcoin sidechain
- Operator: Blockstream + federation of ~15 institutions
- Block time: 2 minutes (vs Bitcoin's ~10 min)
- Finality: ~4 minutes (2 confirmations)
- Privacy: Confidential Transactions + Confidential Assets (default)
- Peg: L-BTC = BTC 1:1 (federation multisig HSM)
- Framework: Elements (Blockstream open-source)