Bitcoin L2 Speed Comparison: Lightning vs Spark vs Liquid vs Ark
Compare transaction speeds and finality across Bitcoin Layer 2 protocols including Lightning, Spark, Liquid, Ark, Stacks, and RSK.
Transaction Speed Across Bitcoin Layer 2 Protocols
Bitcoin's base layer processes 3 to 7 transactions per second with a 10-minute average block time. That throughput is sufficient for settlement, but far too slow for payments, trading, or any application that requires near-instant confirmation. Bitcoin Layer 2 protocols solve this by moving transaction execution off-chain while anchoring security to the base layer, but they take fundamentally different approaches to speed, finality, and trust.
The following table compares confirmation time, finality type, and throughput across the six most widely deployed Bitcoin L2s. Each protocol makes distinct tradeoffs between speed, decentralization, and the trust assumptions required of users.
| Protocol | Type | Confirmation Time | Finality Type | Throughput | Requires Channels |
|---|---|---|---|---|---|
| Lightning Network | Payment channels | <1 second | Instant (channel-level) | 1M+ TPS (theoretical) | Yes |
| Spark | Statechain | <1 second | Instant (no channels) | High (off-chain) | No |
| Liquid Network | Federated sidechain | ~2 minutes | Deterministic (2 blocks) | ~7 TPS | No |
| Ark | VTXO-based | <1 second (OOR) / minutes (rounds) | Delayed (round-based) | Configurable per ASP | No |
| Stacks | Proof of Transfer | ~5 seconds | Bitcoin finality | ~50 TPS | No |
| Rootstock (RSK) | Merge-mined sidechain | ~30 seconds | Probabilistic | ~11 TPS | No |
For a broader comparison that includes fee structures, see our Bitcoin L2 fee comparison. For an overview of trust models and architecture, see the Bitcoin Layer 2 comparison research article.
Lightning Network: Sub-Second Payments via Channels
The Lightning Network routes payments through a network of bidirectional payment channels using HTLCs. Once a channel is open, payments settle in under 500 milliseconds under optimal routing conditions. Each channel can theoretically handle around 500 transactions per second, and the network's aggregate capacity scales with the number of active channels.
Lightning achieves true instant finality at the channel level: once a payment completes its multi-hop route, the balances are updated and cryptographically committed. No further confirmation is needed. However, opening and closing channels requires on-chain Bitcoin transactions, which means users face base-layer confirmation times (10+ minutes) and fees for channel management operations.
The tradeoff is operational complexity. Users must maintain sufficient inbound liquidity, manage channel balances, and deal with routing failures on large payments. Payment success rates exceed 99% for well-connected nodes, but the experience degrades for infrequent users without an LSP handling channel management.
Spark: Instant Finality Without Channels
Spark is a Bitcoin L2 built on statechain technology with FROST threshold signing. Transactions settle in under one second with instant finality, similar to Lightning, but without requiring users to open channels or manage liquidity. Spark uses a cooperative signing model where ownership of a UTXO is transferred off-chain through key rotation among a threshold set of signers.
This architecture eliminates the channel management overhead that makes Lightning complex for end users. There is no concept of inbound or outbound capacity: users can receive any amount at any time. Spark also natively supports tokens, including the USDB stablecoin, enabling instant dollar-denominated payments on Bitcoin without bridging to another chain.
Spark maintains Lightning compatibility, allowing users to send and receive payments across both networks. For a detailed technical breakdown, see our research article on what Spark is and how it works.
Liquid Network: Deterministic 2-Minute Finality
The Liquid Network is a federated sidechain operated by a consortium of functionaries. Blocks are produced every 60 seconds in a round-robin signing process, with no proof-of-work variance. A transaction is considered final after 2 confirmations, giving a typical settlement time of approximately 2 minutes.
Unlike Lightning or Spark, Liquid's finality is deterministic at the block level: once a block is signed by the federation, its parent block can never be reorganized. This makes Liquid well-suited for trading and institutional settlement where predictable confirmation times matter more than sub-second speed. Liquid also supports confidential transactions that hide amounts and asset types from third-party observers.
The throughput limitation is that Liquid blocks have the same maximum weight as Bitcoin blocks, and confidential transactions are larger than standard ones. The result is roughly similar per-block transaction capacity to Bitcoin, but with 10 times the block frequency. Security depends entirely on the federation rather than Bitcoin's full proof-of-work, which represents a meaningful trust assumption compared to channel-based or statechain-based protocols.
Ark: Instant Transfers with Delayed Settlement
Ark introduces a novel approach using virtual transaction outputs (VTXOs) managed by an Ark Service Provider (ASP). Ark supports out-of-round (OOR) payments that settle instantly between users without waiting for on-chain rounds. These OOR transfers are fast and do not require liquidity, but they carry a trust assumption: until the receiver refreshes their balance in a round, they must trust that the sender and ASP do not collude to double-spend.
For full on-chain finality, users participate in periodic rounds where the ASP batches multiple transfers into a single Bitcoin transaction. Round intervals are configurable per ASP and are expected to range from minutes to roughly an hour. VTXOs have a limited lifetime (typically around 30 days), after which users must refresh them or exit to the base layer.
Ark's speed profile is therefore split: instant for everyday payments (with trust in the ASP) and slower for trustless settlement. This design targets the same simplicity goals as Spark but through a different mechanism. For a direct comparison, see our Lightning vs Ark comparison.
Stacks: 5-Second Blocks with Bitcoin Finality
Stacks uses Proof of Transfer (PoX), where miners spend BTC to mine STX blocks. The Nakamoto upgrade, activated in October 2024, reduced block times from approximately 10 minutes down to around 5 seconds. This was the single largest performance improvement in Stacks' history.
The Nakamoto upgrade also introduced 100% Bitcoin finality: once a Stacks transaction is confirmed, reversing it is at least as difficult as reversing a Bitcoin transaction. The Stacks blockchain no longer forks independently from Bitcoin. This gives Stacks stronger finality guarantees than most sidechains, though the 5-second block time still makes it slower than Lightning or Spark for pure payment use cases.
Stacks is primarily a smart contract platform (using the Clarity language) rather than a payment-focused L2. Its speed improvements benefit DeFi applications, NFT markets, and programmable Bitcoin use cases more than point-of-sale payments.
Rootstock (RSK): Merge-Mined EVM Sidechain
Rootstock is a merge-mined sidechain that produces blocks every 30 seconds on average, secured by over 87% of Bitcoin's hashrate as of mid-2025. It provides EVM compatibility, enabling Solidity smart contracts to run on a Bitcoin-anchored chain.
Finality on RSK is probabilistic, similar to Bitcoin itself but faster due to shorter block intervals. Transactions gain increasing security with each confirmation. The merge-mining model provides substantial hashrate security without requiring separate mining infrastructure, though the federated bridge (Powpeg) for moving BTC between Bitcoin and RSK introduces its own trust assumptions.
RSK's real-world throughput is approximately 11 simple transactions per second, with the roadmap targeting faster block times (potentially 10 seconds) through protocol improvements. Like Stacks, RSK is optimized for smart contract execution rather than raw payment speed.
Finality Models Compared
The meaning of "finality" differs significantly across these protocols. Understanding these distinctions is critical for choosing the right L2 for a given use case. For a deeper analysis, see our research on payment finality across blockchains.
| Protocol | Finality Model | Time to Finality | Reorg Risk | Trust Requirement |
|---|---|---|---|---|
| Lightning | Instant (cryptographic commitment) | <1 second | None (channel-level) | Counterparty + routing nodes |
| Spark | Instant (statechain transfer) | <1 second | None | Threshold signer set |
| Liquid | Deterministic (federation-signed blocks) | ~2 minutes | None after 2 confirmations | Federation of functionaries |
| Ark | Instant (OOR) / delayed (rounds) | <1 sec (OOR) / minutes+ (round) | ASP collusion risk for OOR | ASP operator |
| Stacks | Bitcoin finality (post-Nakamoto) | ~5 seconds | Same as Bitcoin | PoX miners |
| RSK | Probabilistic (merge-mined PoW) | ~30 seconds (1 block) | Decreases with confirmations | Merge-miners + Powpeg federation |
Speed vs. Decentralization Tradeoffs
No Bitcoin L2 achieves maximum speed, maximum decentralization, and minimal trust simultaneously. Each protocol sits at a different point on this spectrum, and the right choice depends on the use case.
Payment-optimized protocols (Lightning, Spark, Ark):
- Fastest confirmation times (sub-second) but rely on specific infrastructure: channels for Lightning, statechain operators for Spark, and ASPs for Ark
- Designed for high-frequency, low-value transfers where instant settlement matters
- Spark and Ark eliminate channel management complexity at the cost of trusting a signing entity, though users retain unilateral exit capability
Sidechain protocols (Liquid, RSK):
- Moderate speed (30 seconds to 2 minutes) with broader programmability
- Security depends on a federation (Liquid) or merge-mining hashrate (RSK) rather than Bitcoin's full consensus
- Better suited for trading, institutional settlement, and smart contract applications where predictable block times outweigh sub-second latency
Smart contract platforms (Stacks):
- 5-second block times with Bitcoin-equivalent finality after the Nakamoto upgrade
- Optimized for DeFi, NFTs, and programmable Bitcoin rather than raw payment speed
- Unique among Bitcoin L2s in achieving Bitcoin finality without federation trust
For a detailed analysis of trust models across these protocols, see our research on Bitcoin L2 trust model comparison.
Choosing the Right Protocol by Use Case
Point-of-sale and retail payments: Lightning and Spark both deliver sub-second confirmation, which is the minimum threshold for in-person payment experiences. Spark's advantage is eliminating channel setup for new users, while Lightning benefits from a larger existing merchant network.
Cross-border remittances: Spark and Lightning both support instant transfers at near-zero cost. Spark's native support for USDB stablecoins adds the ability to send dollar-denominated value without BTC price exposure.
Institutional trading and settlement: Liquid's deterministic 2-minute finality and confidential transactions make it the standard for exchanges and OTC desks that need predictable settlement without exposing trade details.
DeFi and programmable Bitcoin: Stacks (Clarity) and RSK (Solidity) provide smart contract functionality. Stacks offers stronger Bitcoin finality, while RSK provides EVM compatibility for teams with existing Ethereum tooling.
For a guided decision framework, see our Layer 2 comparison tool.
Frequently Asked Questions
Which Bitcoin Layer 2 is the fastest?
Lightning and Spark both confirm transactions in under one second, making them the fastest Bitcoin L2s for payment use cases. Ark's out-of-round payments also settle instantly but carry additional trust assumptions. Stacks confirms in about 5 seconds, Rootstock in about 30 seconds, and Liquid in approximately 2 minutes.
What is the difference between instant finality and probabilistic finality on Bitcoin L2s?
Instant finality means a transaction is irreversible the moment it completes: Lightning and Spark achieve this through cryptographic commitments and statechain transfers, respectively. Probabilistic finality (used by RSK) means a transaction becomes progressively harder to reverse with each additional block confirmation but is never theoretically impossible to revert. Deterministic finality (Liquid) falls between the two: once the federation signs a block, its parent is permanently committed.
Does Spark require payment channels like Lightning?
No. Spark uses statechain technology with FROST threshold signing instead of payment channels. Users do not need to lock funds into channels, manage inbound liquidity, or worry about channel capacity limits. This makes Spark simpler to use while maintaining sub-second transaction speeds comparable to Lightning.
How does Liquid Network finality work?
Liquid produces blocks every 60 seconds through a federation of functionaries who sign blocks in a round-robin process. A transaction is considered final after 2 block confirmations (approximately 2 minutes). Unlike Bitcoin's probabilistic finality, Liquid's finality is deterministic: once a block is signed, its parent block cannot be reorganized. The tradeoff is that security depends on the federation rather than proof-of-work.
What is Ark's out-of-round payment and how fast is it?
Out-of-round (OOR) payments allow Ark users to transfer VTXOs to each other instantly without waiting for the next on-chain round. These payments settle in under a second and do not require liquidity. However, OOR payments carry a trust assumption: until the receiver refreshes their balance in a round transaction, they trust the sender and the ASP not to double-spend. Full trustless settlement occurs only when a round transaction is confirmed on Bitcoin.
How did the Stacks Nakamoto upgrade improve transaction speed?
The Nakamoto upgrade, activated in October 2024, reduced Stacks block times from approximately 10 minutes to around 5 seconds. It also introduced 100% Bitcoin finality, meaning Stacks transactions are as hard to reverse as Bitcoin transactions. Before Nakamoto, Stacks blocks followed Bitcoin's 10-minute cadence and could fork independently, making the network too slow for most real-time applications.
Can Bitcoin L2s process more transactions per second than Visa?
Lightning's theoretical throughput exceeds 1 million TPS across the network because each payment channel processes transactions independently. In practice, throughput depends on channel availability and routing efficiency. Visa processes roughly 1,700 TPS on average (with capacity for 65,000 TPS). Off-chain L2s like Lightning and Spark can match or exceed this in aggregate, while on-chain L2s like Liquid, Stacks, and RSK are limited to tens of TPS. For a direct comparison, see our Lightning vs Visa comparison.
This tool is for informational purposes only and does not constitute financial advice. Performance data is approximate and based on publicly available documentation, protocol specifications, and real-world benchmarks as of mid-2026. Throughput, latency, and finality characteristics may change as protocols are upgraded. Always consult official documentation before making architectural decisions.
Build with Spark
Integrate bitcoin, Lightning, and stablecoins into your app with a few lines of code.
Read the docs →
