Tools/Explorers

Lightning LSP Comparison: Channel Liquidity Providers

Compare Lightning LSPs by fee structure, channel size, JIT channel support, zero-conf availability, privacy practices, and LSPS specification compliance.

Spark Team

Lightning LSP Comparison Overview

A Lightning Service Provider (LSP) manages channel liquidity on behalf of wallet users. When you receive a Lightning payment, someone needs to have already committed bitcoin to a channel pointing at you. LSPs solve this by opening channels on demand, providing inbound liquidity, and handling the on-chain transactions that keep channels funded. Without an LSP, every Lightning user would need to run their own node, find channel partners, and lock up capital manually.

The LSP landscape has consolidated since 2024. Voltage deprecated its Flow 2.0 product in September 2025. Breez deprecated its Greenlight SDK in May 2025, shifting to Liquid-based swaps. Mutiny Wallet shut down entirely. The remaining active LSPs serve different niches: ACINQ powers Phoenix, Olympus serves ZEUS, Blocktank backs Bitkit, and LQwD operates as an infrastructure-layer routing and liquidity provider.

The following table summarizes the major LSPs that actively manage channel liquidity for end users and developers.

LSPOperatorPrimary WalletJIT ChannelsZero-ConfLSPS ComplianceStatus
ACINQACINQPhoenixYes (via splicing)YesNo (proprietary protocol)Active
BreezBreez TechnologyBreez WalletYesYesPartial (LSPS2)Transitioning to Liquid
OlympusZEUS LNZEUSYesYesYes (LSPS1)Active
BlocktankSynonymBitkitYes (CJIT)Yes (capped)PartialActive
LQwDLQwD TechnologiesNone (B2B)NoNoNoActive (routing focus)
Voltage FlowVoltageMutiny (defunct)YesYesPartialDeprecated (Sep 2025)

For a broader look at LSP SDKs and integration options for developers, see our Lightning Service Provider SDK comparison.

Fee Structure Comparison

LSP fees have two components: a liquidity fee (percentage or flat rate for the capital the LSP commits) and a mining fee (the on-chain transaction cost for opening or splicing a channel). The liquidity fee is the LSP's revenue. The mining fee fluctuates with mempool conditions and is passed through to the user.

The table below compares current fee structures. Mining fees are excluded because they vary with network congestion and are not controlled by the LSP.

LSPChannel Open / Liquidity FeeSending FeeFirst-Receive SetupMin Channel SizeMax Channel Size
ACINQ (Phoenix)1% of inbound liquidity (min 3,000 sats) + mining fee for splice0.4% + 4 sats1,000 sats one-time~10,000 sats~16M sats (single channel via splicing)
Breez0.4% of received amount + mining feeRouting fees onlyIncluded in channel open fee~20,000 sats~4M sats
Olympus (ZEUS)Tiered: 50% under 20 sats, 10% under 2,500 sats, 250 sats flat above0 sats (first hop free)Included~20,000 sats~10M sats aggregate
Blocktank (Bitkit)Service fee + mining fee (varies by order size)Routing fees onlyIncluded~1,000 sats~3.17M sats
LQwDNegotiated (B2B contracts)Standard routing feesN/ANegotiatedNegotiated
Note: Fee structures change frequently. The figures above reflect publicly available data as of late 2026. Always check the provider's current documentation before committing capital.

How JIT Channels and Splicing Work

Just-in-time (JIT) channel opening allows an LSP to create a channel at the exact moment a user receives a payment, rather than requiring pre-allocated liquidity. The incoming payment itself funds the channel. This is defined formally in the LSPS2 specification, which was finalized as bLIP-52 in January 2025.

ACINQ's Phoenix takes a different approach. Instead of opening new channels on each receive, Phoenix maintains a single dynamic channel that resizes through on-chain splices. When you receive more than your current inbound capacity allows, Phoenix executes a splice-in transaction that adds capacity to the existing channel. This avoids channel proliferation but requires an on-chain transaction for each capacity increase.

Olympus and Breez use the traditional JIT model: a new zero-conf channel opens instantly when a payment arrives, without waiting for on-chain confirmation. The user trusts the LSP not to double-spend the channel funding transaction during the confirmation window.

Privacy Considerations

Every LSP has visibility into some of your payment activity by design. The question is how much, and what they do with it.

  • ACINQ (Phoenix) uses trampoline routing, which means ACINQ's node sees the final destination of every payment you send. Phoenix supports Tor connections to hide your IP address, and ACINQ's App Store privacy label states the app does not collect user data. However, the trampoline architecture gives ACINQ the technical ability to correlate sender, receiver, and amount for every outbound payment.
  • Breez operates as both the LSP and the first routing hop. Breez can see the amount and timing of channel opens but does not necessarily see the final payment destination if multi-hop routing is used.
  • Olympus (ZEUS) provides the first hop at zero routing fees. ZEUS supports running your own embedded LND node, giving users more control over routing decisions. However, Olympus still sees inbound payment amounts and channel states.
  • Blocktank (Bitkit) sees channel open amounts and can correlate on-chain funding transactions. The Bitkit wallet connects directly to Synonym's infrastructure.
  • LQwD operates as a routing node provider rather than a direct-to-user LSP. It sees standard routing information (amount, timing, HTLC details) for payments it routes, like any other routing node.

None of these LSPs publish formal, auditable privacy policies that specify data retention periods or what metadata they log. Users who require strong payment privacy should evaluate blinded paths (available in BOLT12) or protocols that avoid channel-based architectures altogether.

LSPS Specification Compliance

The LSPS specifications define a standard protocol for how wallets communicate with LSPs. The core specs were finalized as Bitcoin Lightning Improvement Proposals (bLIPs) in January 2025:

  • LSPS0 (bLIP-50): transport layer using JSON-RPC 2.0 over BOLT 8 custom peer messages (message type 37913)
  • LSPS1 (bLIP-51): pre-purchased channel opens, where the wallet requests a channel of a specific size and pays upfront
  • LSPS2 (bLIP-52): JIT channel opens, where the LSP opens a channel on the fly when a payment arrives, deducting its fee from the forwarded amount

LSPS compliance matters because it determines whether a wallet can switch between LSPs without code changes. A wallet built against LSPS1 can theoretically work with any LSPS1-compliant LSP. Without standardization, wallets are locked into a single provider.

In practice, adoption is uneven. Olympus supports LSPS1 and integrates with both ZEUS and Alby Hub. The LDK lightning-liquidity crate implements LSPS0, LSPS1, and LSPS2, though its service-side code is still marked as beta. ACINQ chose a different path: Phoenix uses a proprietary protocol built around dual-funded channels, splicing, and liquidity ads rather than adopting the LSPS specs. This makes Phoenix tightly coupled to ACINQ's infrastructure.

For a deeper analysis of LSPS progress and adoption timelines, see our research on how LSPS standards are shaping mobile wallets.

The Core Problem LSPs Solve (and Create)

LSPs exist because the Lightning Network requires pre-funded payment channels. Before you can receive a single satoshi, someone must lock bitcoin into a channel with you. This creates a bootstrapping problem: new users have no channels, no inbound capacity, and no way to receive payments without help.

LSPs solve bootstrapping but introduce their own issues:

  • Vendor lock-in: Phoenix only works with ACINQ. If ACINQ raises fees or shuts down, Phoenix users must migrate to a different wallet entirely.
  • On-chain cost exposure: every new channel or splice requires an on-chain transaction. During fee spikes, a single channel open can cost thousands of sats in mining fees.
  • Capital inefficiency: the LSP must lock bitcoin in channels that may sit idle, and users pay for that capital cost through liquidity fees.
  • Trust for zero-conf: JIT channels are usable before on-chain confirmation, but only because the user trusts the LSP not to double-spend the funding transaction.

These tradeoffs are inherent to any channel-based architecture. For a detailed cost breakdown, see the Lightning channel cost calculator.

How Spark Eliminates the Need for LSPs

Spark is a Bitcoin Layer 2 built on a statechain architecture that transfers UTXO ownership off-chain without payment channels. Because there are no channels, there is no inbound liquidity problem, no channel management, and no need for an LSP.

In Spark's model, ownership of a bitcoin UTXO is represented by a cryptographic key share held jointly by the user and a set of operators using FROST threshold signatures. Transferring value means rotating the key share to the new owner, not routing a payment through a channel graph. This eliminates the capital lockup, on-chain fees, and privacy tradeoffs that LSPs introduce.

Spark uses Spark Service Providers (SSPs) instead of LSPs. SSPs handle Lightning interoperability through atomic swaps: when a Spark user pays a Lightning invoice, the SSP executes a trustless swap where both legs complete or neither does. SSPs do not need to pre-fund channels for individual users, and users can exit to Bitcoin L1 at any time without permission from the SSP.

For a full architectural comparison, see our research on why Spark's channel-free design eliminates LSP dependency.

Which LSP Is Cheapest for Small Channels?

For users receiving small amounts (under 50,000 sats), Olympus is typically the cheapest LSP. Its tiered fee structure charges a flat 250 sats for payments above 2,500 sats, which works out to 0.5% on a 50,000 sat receive. ACINQ's 1% liquidity fee with a 3,000 sat minimum makes Phoenix more expensive for small receives: a 50,000 sat inbound payment costs 3,000 sats minimum plus mining fees.

For very small receives (under 2,500 sats), all LSPs become expensive in percentage terms. Olympus charges 10% on amounts between 20 and 2,500 sats. Phoenix's 3,000 sat minimum means a 5,000 sat receive costs 60% in liquidity fees alone, before mining fees.

Breez's 0.4% rate is competitive for medium-sized channel opens (100,000+ sats), where the percentage-based fee stays low relative to the amount. However, Breez's transition toward Liquid-based swaps means the channel-opening model may not be available long-term.

The cheapest option for small, frequent payments is to avoid channel-based architectures entirely. Spark transfers have no channel-opening fees because there are no channels to open. The liquidity marketplace comparison covers additional options for sourcing inbound capacity.

Frequently Asked Questions

Do I need an LSP if I use Spark?

No. Spark uses a statechain-based architecture that does not require payment channels. Because there are no channels, there is no need for an LSP to provide inbound liquidity or manage channel state. Spark Service Providers (SSPs) handle Lightning interoperability through atomic swaps, but they serve a fundamentally different role than LSPs: SSPs do not pre-fund channels or lock capital for individual users.

What happens if my LSP goes offline or shuts down?

If your LSP goes offline, you can still close your channels cooperatively or force-close them on-chain to recover your funds. However, you will lose the ability to receive new payments until you connect to a different LSP or open channels manually. This is what happened when Voltage deprecated Flow 2.0 in September 2025: wallets that depended on Voltage for liquidity had to find alternative providers or migrate to different wallet software entirely.

Which Lightning LSP has the best privacy?

No LSP offers strong privacy guarantees. All LSPs see channel open amounts, on-chain funding transactions, and payment timing. ACINQ has the most visibility because Phoenix uses trampoline routing, which reveals payment destinations to ACINQ's node. Olympus (ZEUS) offers more routing flexibility because ZEUS runs an embedded LND node, letting users choose their own routes after the first hop. For payment privacy beyond what any LSP can provide, consider protocols that support blinded paths or avoid channels altogether.

What is the difference between LSPS1 and LSPS2?

LSPS1 (bLIP-51) covers pre-purchased channel opens: the wallet requests a channel of a specific size and pays upfront before the channel is created. LSPS2 (bLIP-52) covers just-in-time (JIT) channel opens: the LSP opens a channel on the fly when an incoming payment arrives and deducts its fee from the forwarded amount. LSPS1 is better for predictable liquidity needs, while LSPS2 is better for wallets that want to onboard users with zero upfront cost.

Can I switch between LSPs without losing funds?

Yes, your funds are always in self-custodial channels that you can close at any time. Switching LSPs means closing your current channels (which requires an on-chain transaction and a wait for confirmation), then opening new channels with a different LSP. If both LSPs support LSPS1 or LSPS2, your wallet may be able to connect to the new provider without code changes. In practice, most wallets are tightly integrated with a single LSP, so switching often means switching wallets.

Why are small Lightning channels so expensive?

Small channels are expensive because the on-chain mining fee for opening a channel is fixed regardless of channel size. A channel open that costs 2,000 sats in mining fees represents 4% of a 50,000 sat channel but only 0.02% of a 10 million sat channel. LSP liquidity fees compound this: ACINQ's 3,000 sat minimum means any receive under 300,000 sats pays more than 1% in liquidity fees alone. This fixed-cost problem is a fundamental limitation of channel-based architectures, which is why protocols like Spark and Ark pursue channel-free designs.

Are zero-conf channels safe?

Zero-conf channels are safe in practice but not trustless. When an LSP opens a zero-conf channel, the funding transaction has not yet been confirmed on-chain. The user trusts the LSP not to double-spend that transaction. Reputable LSPs have no incentive to double-spend because it would destroy their reputation and business. However, the trust assumption is real: if the LSP is malicious or compromised, it could broadcast a conflicting transaction before the channel funding confirms.

This tool is for informational purposes only and does not constitute financial advice. Fee data is approximate, based on publicly available documentation, and subject to change. LSP fee structures fluctuate with network conditions and provider updates. Always verify current pricing with the LSP directly before committing funds.

Build with Spark

Integrate bitcoin, Lightning, and stablecoins into your app with a few lines of code.

Read the docs →