Why Bitcoin Needs More Than One Layer
Bitcoin's base layer prioritizes security and decentralization above all else. Ten-minute block times, a global mempool, and full on-chain verification make Bitcoin the most secure monetary network ever built, but they also create real constraints: limited throughput, slow confirmation times, and fully transparent transactions.
No single approach can address all of those constraints at once. A system optimized for instant micropayments looks very different from one optimized for private, high-value settlement. That is why Bitcoin has two major networks beyond the base layer, a layer-2 (Lightning) and a sidechain (Liquid), each designed around a distinct set of trade-offs.
The Lightning Network and the Liquid Network both extend what bitcoin can do without weakening the base layer. But they take different approaches, serve different use cases, and make different trade-offs. Understanding those differences is the key to choosing the right tool for each situation.
Lightning Network: Instant Payments at Scale
The Lightning Network is a payment channel network that sits on top of Bitcoin. It enables near-instant transactions with fees measured in fractions of a satoshi. Where the Bitcoin base layer handles roughly 7-15 transactions per second post-SegWit (depending on transaction mix, since simple Taproot transactions take less space than complex multisig), Lightning's throughput scales with channel liquidity and routing capacity, not constrained by a fixed protocol-level block interval.
How Lightning Works
Lightning operates through a network of bilateral payment channels. Two parties lock bitcoin into an on-chain multisig transaction, creating a channel between them. Once the channel is open, they can send payments back and forth instantly, updating their shared balance as many times as they want without touching the blockchain. When they are done, they close the channel and settle the final balance on-chain.
The power of Lightning comes from routing. You do not need a direct channel with every person you want to pay. If Alice has a channel with Bob, and Bob has a channel with Carol, Alice can pay Carol by routing the payment through Bob. Hash Time-Locked Contracts (HTLCs) ensure that every hop in the route either completes atomically or fails entirely, so no one can steal funds along the way. HTLCs work by requiring each hop to reveal a preimage, the secret value whose hash equals the payment hash, within a time window. If the preimage is revealed, the payment succeeds at that hop. If the time lock expires, the funds revert to the sender. This is defined in BOLT 2 (channel operation) and BOLT 3 (transaction formats) of the Lightning specification.
The result is a network where payments settle in seconds, cost almost nothing, and still inherit Bitcoin's security guarantees through the on-chain channel funding transactions.
What Lightning Does Best
- Instant payments. Lightning transactions settle in seconds, making it suitable for point-of-sale purchases where a customer is standing at a counter.
- Micropayments. Fees are low enough to send a single satoshi. This enables use cases like pay-per-article content, streaming sats for podcasts, and machine-to-machine payments.
- High throughput. Because transactions happen off-chain inside channels, Lightning can handle a volume of payments that the base layer never could.
- Growing merchant adoption. From coffee shops to online retailers, Lightning acceptance has expanded significantly as wallet software and payment infrastructure have matured.
Lightning's Trade-offs
- Channel capacity limits. You cannot send more bitcoin through a channel than the channel holds. Large payments may need to be split across multiple routes, and finding sufficient liquidity for very large transfers can be difficult.
- Online requirement. Both parties in a channel need to monitor the blockchain to ensure neither side broadcasts an outdated channel state. In practice, this means running a node or trusting a watchtower service.
- Moderate privacy. Channel openings and closings are visible on-chain, and routing nodes can observe payment amounts passing through them. Lightning is more private than on-chain transactions in some ways, but less private than systems with built-in transaction confidentiality.
- Bitcoin only. Lightning moves bitcoin. It does not support other assets like stablecoins or security tokens.
Core Lightning (CLN), Blockstream's Lightning implementation, is one of the major open-source Lightning node implementations. Built in C and Rust for performance and modularity, CLN powers a significant portion of the Lightning Network's routing infrastructure and is the foundation for many Lightning-based applications and services.
Liquid Network: Private Settlement and Asset Issuance
The Liquid Network is a federated sidechain that extends Bitcoin with faster settlement, built-in transaction privacy, and the ability to issue new assets. Where Lightning optimizes for speed and micropayments, Liquid optimizes for confidentiality, asset versatility, and reliable settlement without capacity constraints.
How Liquid Works
Liquid operates as a sidechain anchored to Bitcoin. Users peg in by sending bitcoin to an address controlled by the Liquid Federation, a geographically distributed group of functionary operators that includes exchanges, financial institutions, and infrastructure companies. In return, the user receives an equal amount of Liquid bitcoin (LBTC) on the Liquid sidechain. To move back, they peg out and receive bitcoin on the mainchain.
The federation produces blocks approximately every minute using a round-robin signing protocol. At each block interval, a designated proposer assembles a candidate block and signs it, then the remaining active signers validate and co-sign using an 11-of-15 threshold. Transactions reach final settlement after two confirmations (roughly two minutes). In practice there is no mempool congestion or fee auction, and a valid transaction typically confirms in the next block. The federation consensus logic is implemented in Elements Core, Blockstream's open-source sidechain framework.
Every Liquid transaction uses Confidential Transactions by default, a cryptographic protocol that hides both the transaction amount and the asset type from outside observers. Only the sender, the receiver, and anyone they choose to share a blinding key with can see the details. This privacy is built into the protocol itself.
What Liquid Does Best
- Transaction privacy. Confidential Transactions hide both amounts and asset types by default.
- Larger value transfers. Liquid has no channel capacity limits. A transfer of 100 LBTC uses the same process as a transfer of 0.001 LBTC. Settlement is predictable regardless of amount.
- Fast, predictable settlement. One-minute block times with deterministic finality after two confirmations. No fee bidding, no mempool delays.
- Asset issuance. Anyone can issue new assets on Liquid: stablecoins (USDT circulates on Liquid), security tokens, collectibles, or any programmable asset. These Issued Assets inherit the same Confidential Transactions privacy as LBTC.
- Smart contracts. The Simplicity smart contract language, designed for formal verification, enables expressive programmability on Liquid while maintaining the ability to mathematically prove that contracts behave as intended.
Liquid's Trade-offs
- Federation trust model. The Liquid Federation is a defined group of entities, not an open set of miners. Users trust that a threshold of federation members will act honestly. This is a different security model than Bitcoin's proof-of-work, with different trust assumptions.
- One-minute blocks, not instant. Liquid is significantly faster than the Bitcoin base layer but slower than Lightning for point-of-sale scenarios where sub-second settlement matters.
- Peg-in time. Moving bitcoin onto Liquid requires 102 Bitcoin block confirmations (roughly 17 hours). Peg-outs are faster but still require federation processing. Once bitcoin is on Liquid, transfers between Liquid users are fast.
Security Model Comparison
Lightning and Liquid take fundamentally different approaches to security, and the tradeoffs shape which use cases each network serves best.
Lightning: Channel-Based Security
Lightning's security derives directly from the Bitcoin base layer. Each payment channel is anchored by an on-chain 2-of-2 multisig transaction that locks bitcoin between two parties. The channel's state (who owns how much) is tracked off-chain through a series of commitment transactions that either party can broadcast to settle on-chain at any time. The revocation mechanism (defined in BOLT 3) penalizes a party that broadcasts an outdated state by allowing the counterparty to claim all funds in the channel. This creates a trustless system where no party can cheat without risking the loss of their entire channel balance.
The tradeoff: Lightning requires active monitoring. If a counterparty broadcasts a revoked commitment transaction and the other party fails to respond within the timelock window (typically 144 to 2016 blocks), the cheating party can claim funds. This is why Lightning users either run their own node or delegate monitoring to a watchtower service. Lightning's security is anchored in Bitcoin's proof-of-work, but it is a different operational model that requires ongoing participation to enforce.
Liquid: Federation-Based Security
Liquid's security rests on the Liquid Federation, a geographically distributed set of functionary operators that collectively sign blocks and manage the bitcoin peg. Both block production and peg custody use an 11-of-15 multisig, meaning at least 11 of the 15 active functionaries must cooperate to produce a block or authorize a peg-out. An attacker would need to compromise or coerce at least 11 independent entities across multiple jurisdictions to steal funds or censor transactions.
The tradeoff: Liquid introduces a trust assumption that Lightning does not. Users trust that a supermajority of federation members will act honestly. Federation members are publicly identified companies with reputational and legal exposure, which creates strong disincentives against collusion. An emergency time-locked recovery mechanism protects the pegged bitcoin if the federation becomes non-functional. Liquid's security model trades Bitcoin's trustless proof-of-work guarantee for faster settlement, Confidential Transactions, and asset issuance capabilities that Lightning's channel architecture cannot support.
Side-by-Side Comparison
The following table compares Lightning and Liquid across the dimensions that matter most when choosing between them.
| Feature | Lightning Network | Liquid Network |
|---|---|---|
| Speed | Near-instant (seconds) | ~1-minute blocks; final after ~2 minutes |
| Privacy | Moderate. Channel open/close visible on-chain; routing nodes see payment amounts. | Strong. Confidential Transactions hide both amounts and asset types by default. |
| Best Transaction Size | Small to medium. Limited by channel capacity and route liquidity. | Any size. No capacity limits on individual transactions. |
| Security Model | Payment channels secured by on-chain multisig + HTLCs. Inherits Bitcoin PoW security. | Federated sidechain. Trust distributed across a threshold of geographically diverse federation members. |
| Asset Support | Bitcoin only | LBTC, USDT, and any Issued Assets (security tokens, stablecoins, etc.) |
| Online Requirement | Must monitor channels (run a node or use a watchtower) | No ongoing online requirement. Receive and hold LBTC offline. |
| Capacity Limits | Limited by channel capacity and network liquidity | No per-transaction capacity limits |
| Smart Contracts | Limited (HTLCs; PTLCs proposed) | Simplicity: formally verifiable smart contract language |
| Hardware Wallet Support | Limited. Lightning's channel management model does not map well to offline signing. | Native. Jade Plus signs Liquid transactions with air-gapped QR codes. |
| Primary Use Cases | Point-of-sale payments, micropayments, streaming sats, instant P2P transfers | Private transfers, trading settlement, asset issuance, larger value transfers, tokenization |
When to Use Lightning
Lightning is the right choice when speed and low cost matter more than privacy or transaction size.
Point-of-Sale Payments
A customer scanning a QR code at a register needs the payment to confirm before they walk away. Lightning settles in seconds. For merchants, this means no waiting for block confirmations and no risk of double-spend during the confirmation window.
Micropayments and Streaming Sats
Lightning fees are low enough to make payments of a few sats economically viable. This opens up use cases that are impossible on the base layer: pay-per-second podcast streaming, per-article content paywalls, API metering, and machine-to-machine payments. The base layer's minimum viable transaction amount is constrained by fees; Lightning's is not.
Instant Peer-to-Peer Transfers
Splitting a dinner bill, paying a friend back, or tipping a content creator. Lightning handles these with the immediacy of handing someone cash, but works across any distance. Both parties see the payment settle in real time.
When the Recipient Accepts Lightning
Lightning adoption among merchants and services has grown steadily. If the recipient runs a Lightning node or uses a Lightning-compatible wallet, sending over Lightning is often the fastest and cheapest option. The Blockstream app supports Lightning payments alongside on-chain and Liquid transactions from a single interface, making it straightforward to pay over whichever layer the recipient prefers.
When to Use Liquid
Liquid is the right choice when privacy, transaction size, asset type, or hardware wallet security are priorities.
Privacy-Sensitive Transactions
Every Liquid transaction uses Confidential Transactions by default. The amounts and asset types are cryptographically hidden from anyone not party to the transaction. For individuals who do not want their financial activity visible to every blockchain observer, and for businesses that cannot expose transaction volumes to competitors, this is a baseline requirement.
Trading and Inter-Exchange Settlement
Exchanges that support Liquid can settle with each other in minutes rather than waiting for six on-chain confirmations (roughly an hour). Confidential Transactions mean that settlement volumes between exchanges are not visible to the market. For active traders, moving bitcoin between exchanges on Liquid is faster and more private than on-chain transfers.
Larger Value Transfers
Lightning channels have capacity limits. Routing a large payment requires finding a path with sufficient liquidity at every hop, which becomes unreliable above certain amounts. Liquid has no such constraint. A transfer of any size settles in the same one-minute block cycle with the same fee structure.
Asset Issuance and Tokenization
Liquid supports issuing new assets directly on the sidechain. USDT (Tether) circulates on Liquid. Security tokens, stablecoins, and other digital assets can be issued and transferred using Liquid's infrastructure. Every Issued Asset inherits Confidential Transactions privacy. For organizations building on Bitcoin that need more than a single asset type, Liquid provides the tooling.
Hardware Wallet Security for Layer-2
Lightning's channel-based architecture requires active key management that does not translate well to offline hardware wallet signing. Liquid transactions, by contrast, use a standard UTXO model compatible with hardware wallet workflows. Jade Plus supports Liquid natively, signing LBTC and Liquid asset transactions via air-gapped QR codes with no USB or Bluetooth connection required. For users who want faster and more private settlement without giving up hardware wallet security, Liquid is the only current option.
Institutional Perspective
Which layer suits institutional use cases? For most institutional needs, Liquid is the stronger fit. Confidential Transactions address compliance and competitive sensitivity concerns around exposing transaction data on a public ledger. Predictable one-minute settlement with no capacity limits simplifies treasury operations. Asset issuance enables tokenized securities and stablecoin workflows. The federation security model, which includes regulated financial institutions and major exchanges, aligns more closely with institutional risk frameworks than Lightning's distributed routing network.
Lightning for payment processing, Liquid for treasury and trading. Institutions that process customer-facing payments (merchants, payment service providers, point-of-sale networks) benefit from Lightning's instant settlement and growing acceptance. Institutions focused on treasury management, inter-exchange settlement, or trading benefit from Liquid's privacy, capacity, and multi-asset support. Many institutional operations use both, depending on the flow.
When to Use Both
Lightning and Liquid are not competing standards. They are complementary tools, and cross-layer swaps allow you to move bitcoin between them directly.
Cross-Layer Swaps in Practice
The Blockstream app supports Bitcoin, Lightning, and Liquid from a single interface. It supports Lightning ↔ Liquid swaps natively, letting you shift bitcoin between layers based on what you need at the moment. A practical workflow: receive a Lightning payment from a customer or friend, then swap it to Liquid to store as LBTC on your Jade Plus hardware wallet. The Lightning payment arrives instantly, and the Liquid bitcoin sits in hardware-wallet-secured self-custody with Confidential Transactions privacy.
The reverse works too. Hold LBTC in secure Liquid self-custody, and when you need to make a quick Lightning payment, swap the amount you need and pay instantly. The ability to move freely between layers means you do not have to choose one or the other. You use whichever layer fits the transaction.
Example Scenarios
- A merchant receiving daily Lightning payments can sweep revenue to Liquid at the end of each day, consolidating into LBTC stored on a hardware wallet. Daily transactions settle instantly over Lightning; long-term holdings sit in private, secure Liquid self-custody.
- A trader moving bitcoin between exchanges can use Liquid for fast, private settlement between platforms, then swap to Lightning when they need to pay for goods or services.
- A privacy-conscious user can hold funds as LBTC (Confidential Transactions) and swap to Lightning only at the moment of payment, minimizing the time their transaction activity is observable on any public ledger.
How Both Compare to the Base Layer
Lightning and Liquid exist because the Bitcoin base layer makes deliberate trade-offs that prioritize security and decentralization. Understanding when to stay on-chain versus when to move to one of these networks completes the picture.
When to Stay On-Chain
- Maximum security. For large, infrequent transfers where you want the full weight of Bitcoin's proof-of-work consensus protecting the transaction. The base layer is the most secure settlement network in existence.
- Long-term storage. Bitcoin on the base layer has no dependencies beyond the Bitcoin network itself, unlike a Lightning channel that relies on a counterparty or a Liquid balance that relies on the federation. For cold storage measured in years, on-chain bitcoin has the simplest trust model.
- When the recipient only supports on-chain. Despite growing adoption, not every wallet, exchange, or service supports Lightning or Liquid.
When to Move Off the Base Layer
- Speed matters. If waiting 10 to 60 minutes for confirmations is not acceptable for your use case, either Lightning (seconds) or Liquid (minutes) is the answer.
- Privacy matters. On-chain Bitcoin transactions are fully transparent. If you need to hide transaction amounts and asset types, Liquid's Confidential Transactions provide that by default.
- Cost matters. During periods of high on-chain fee pressure, Lightning and Liquid transactions cost a fraction of what a base-layer transaction costs.
- Functionality matters. If you need to work with stablecoins, issue assets, or use smart contracts, Liquid provides capabilities that the base layer does not.
| Dimension | Bitcoin Base Layer | Lightning Network | Liquid Network |
|---|---|---|---|
| Settlement Time | ~10 min per block; 1-6 confirmations recommended | Seconds | ~1-minute blocks; final in ~2 minutes |
| Security Model | Proof-of-work (most decentralized) | Channels + HTLCs (inherits PoW security) | Federated (distributed trust among members) |
| Privacy | Transparent (all amounts visible) | Moderate (channel states private; routing partially observable) | Strong (Confidential Transactions by default) |
| Throughput | ~7-15 transactions per second post-SegWit | Scales with channel liquidity and routing capacity, not a fixed protocol-level block interval | Higher than base layer; limited by one-minute block interval |
| Best For | High-value settlement, long-term storage, maximum security | Instant payments, micropayments, point-of-sale | Private transfers, trading, asset issuance, larger amounts |
The Future of Bitcoin Layers
The relationship between Lightning and Liquid keeps growing more interconnected over time. Cross-layer swap infrastructure is maturing, making it easier for wallets and services to route transactions across layers automatically based on the needs of each payment.
Growing Interoperability
As cross-layer swaps improve, the distinction between layers becomes less visible to end users. A wallet that holds LBTC can pay a Lightning invoice by performing a swap in the background. A Lightning user can receive into Liquid self-custody without managing the conversion manually. The goal is for users to think about what they want to do (pay, save, trade, issue) rather than which layer to use.
Expanding Use Cases
Liquid's Simplicity smart contract language opens the door to financial instruments, conditional payments, and programmable settlement that were previously impractical on Bitcoin-based systems. Lightning's continued growth in merchant adoption and integration with point-of-sale systems pushes bitcoin closer to functioning as everyday money. Together, they expand what Bitcoin can do while preserving the base layer's role as the anchor of security and decentralization.
Complementary, Not Competing
Lightning and Liquid are different tools built for different jobs. Lightning moves small amounts of bitcoin instantly. Liquid settles larger amounts privately and supports assets beyond bitcoin. The base layer secures everything underneath. Blockstream maintains both Core Lightning and the Liquid Network because building for Bitcoin means building the right tool for each problem, not forcing every use case through a single solution.
Frequently Asked Questions
Is Lightning or Liquid more secure?
They use different security models. Lightning inherits Bitcoin's proof-of-work security through on-chain 2-of-2 multisig channel funding transactions and uses HTLCs with revocation penalties to ensure trustless routing. Anyone broadcasting a revoked channel state risks losing their entire channel balance. Liquid uses a Strong Federation model. Fifteen functionary operators sign each block with an 11-of-15 threshold, and the broader federation (more than 85 member entities as of April 2026) governs membership, oversight, and technical direction. Lightning's security is closer to Bitcoin's own trust model but requires active channel monitoring. Liquid's federation introduces a different set of trust assumptions (trusting the supermajority of known entities) but enables features like Confidential Transactions, asset issuance, and formal-verification-ready smart contracts (Simplicity) that Lightning's channel architecture does not support.
Can I use Lightning and Liquid at the same time?
Yes. The Blockstream app supports Bitcoin, Lightning, and Liquid from a single interface and enables Lightning ↔ Liquid swaps directly within the app. You can receive a Lightning payment and immediately swap it to LBTC on Liquid, or hold LBTC and swap to Lightning when you need to make an instant payment. For hardware security, Jade Plus signs Liquid transactions natively (including Confidential Transactions) via air-gapped QR codes, so you can store your LBTC in cold storage and swap to Lightning only when making payments.
Which is better for large transactions?
Liquid. Lightning payments are constrained by channel capacity and route liquidity, which can make large payments difficult to route. Multipath payments help by splitting a payment across multiple routes, but finding sufficient aggregate liquidity above a few million satoshis can be unreliable. Liquid has no per-transaction capacity limits because it uses a standard UTXO model with a full blockchain. A transfer of 500 LBTC settles just as reliably as a transfer of 0.01 LBTC, with the same one-minute block time and Confidential Transaction privacy.
Do I need to run a node for either one?
For Lightning, running a node (or using a watchtower service) is important for channel security, as you need to monitor the blockchain for outdated channel states. For Liquid, no node is required. You can send, receive, and hold LBTC using any Liquid-compatible wallet without running any infrastructure.
Can I store LBTC on a hardware wallet?
Yes. Jade Plus natively supports Liquid, allowing you to sign LBTC and Liquid asset transactions using air-gapped QR codes. This gives Liquid first-class hardware wallet support for offline transaction signing, which Lightning's architecture does not offer.
Are Lightning and Liquid competing with each other?
No. They serve different use cases and are designed around different trade-offs. Lightning is optimized for instant, small payments using a channel-based off-chain protocol. Liquid is optimized for private settlement, larger transfers, and multi-asset functionality using a federated sidechain with its own blockchain. Many users and institutions use both, choosing the layer that fits each specific transaction. The Blockstream app supports both from a single interface, with built-in cross-layer swaps that make moving between them straightforward.