Lightning Service Providers (LSPs)

In previous lessons, we've discussed how setting up Lightning channels requires capital, on-chain transactions, and technical knowledge. But what if someone else could handle that complexity for you? Enter Lightning Service Providers (LSPs) — businesses that make Lightning accessible to everyone.

What Is an LSP?

A Lightning Service Provider is a business that provides services to make using Lightning easier. Core services include opening channels to users, providing inbound liquidity, managing channel infrastructure, and simplifying the user experience. Think of it like this: an ISP provides internet access while an LSP provides Lightning access.

Why LSPs Matter

The Lightning experience has friction points. For new users, they need to open channels which incur on-chain fees, need inbound liquidity to receive payments, need to understand channel management, and need to run infrastructure or trust someone. LSPs solve these problems by handling channel operations, providing instant inbound capacity, managing complexity behind the scenes, and offering simple user experiences. LSPs are the bridge from "Lightning is complicated" to "Lightning just works."

The LSP Service Model

Channel-as-a-Service means the LSP opens channels to users on demand, the user gets inbound liquidity instantly, and the LSP manages the channel lifecycle. They make money through fees for channel opens, routing fees through their channels, subscription models, and value-added services.

Just-In-Time (JIT) Channels

A key LSP innovation addresses a specific problem. The problem is that a user receives their first Lightning payment but has no channel or inbound liquidity, so the payment would fail. The JIT solution works as follows: a payment comes for the user, the LSP intercepts it, the LSP opens a channel to the user on-the-fly, the payment completes through the new channel, and the user now has a channel with remaining inbound capacity. The result is the ability to receive your first payment without any setup.

How JIT Channels Work (Technical)

First, the user's wallet asks the LSP for a quote and creates an invoice with a route hint through the LSP's node. The hint points to a placeholder channel that doesn't exist yet. When a payment arrives, the LSP holds it instead of forwarding it right away. The LSP then opens a new channel to the user, and the user's wallet accepts it before it is confirmed on-chain, which is known as a zero-conf channel. The LSP forwards the payment through the new channel, keeping its fee for the channel open. Finally, the user receives the sats and has a new channel with inbound capacity. The magic is that the user went from nothing to a funded channel in one step. The tradeoff is that until the channel confirms on-chain, the user trusts the LSP not to double-spend the channel's funding.

Popular LSP Implementations

Phoenix by ACINQ is the best-known example. ACINQ runs the LSP, and the wallet manages a single channel that grows through splicing, so users never have to think about channels. Zeus comes with its own LSP, Olympus, and can also work with other providers. Megalith offers JIT channels and channel purchases to any wallet that supports the open standards. Voltage provides Lightning infrastructure and liquidity for businesses and developers. On the developer side, LDK and Core Lightning include ready-made components for building or connecting to an LSP.

The Tradeoffs

Benefits include dramatically simpler user experience, no upfront capital needed, instant Lightning access, and easy mobile functionality. Costs involve trust in the LSP, fees for services, less control than self-hosting, and potential privacy considerations. The spectrum ranges from full self-custody through LSP-assisted to fully custodial.

LSP Fee Structures

Channel opening fees can be a flat fee per channel, a percentage of the first payment, or included in the service. Ongoing fees include routing fees that are often competitive, subscription fees in some models, and premium features. For example, Phoenix charges 1% plus the mining fee when it needs to add liquidity to receive a payment, while payments that fit your existing channel cost nothing extra to receive.

Privacy Considerations

LSPs typically see your receiving payments since they route them, your channel balances, and your transaction activity through their channels. Mitigations include using multiple LSPs, self-managing some channels, and choosing privacy-focused LSPs. Some wallets, like Phoenix, also let the LSP find the route for outgoing payments, which means the LSP sees who you pay as well. The reality is these are similar privacy tradeoffs to using any Lightning peer, but more concentrated.

LSPs and Wallet Design

LSPs enable better wallet experiences. A traditional wallet requires users to manage channels, source liquidity, and deal with complex UX. An LSP-powered wallet has channels managed automatically, liquidity provided on demand, and a simple "just send/receive" UX. Examples include Phoenix with no visible channels and automatic management, and Zeus offering a hybrid approach where you can use an LSP or manage your own channels.

Running an LSP

If you want to become an LSP, requirements include significant Lightning capital, high-availability infrastructure, technical expertise, customer support capability, and a business structure defining fees and terms. Tools available include the open LSP standards, open-source implementations in LDK and Core Lightning, and custom development. The market for LSP services is still evolving, and there is room for new providers.

The LSP Specification

LSP interfaces are now standardized. The specifications started as LSPS, written by a group of wallet and LSP developers, and were adopted at the end of 2024 as bLIPs, the extension documents for the Lightning protocol. The goals are interoperability between wallets and LSPs, standard APIs, and competition and choice for users. The core pieces are a base protocol for talking to an LSP, a way to buy a channel in advance, a standard for JIT channels, and notifications that wake up a mobile wallet when a payment arrives. LDK, Core Lightning, and wallets like Zeus support them, so a wallet is no longer tied to a single provider.

Choosing an LSP

Consider several factors when selecting an LSP. Reputation matters — look for an established, trustworthy provider. Fees should be competitive and transparent. Reliability means good uptime and quality channels. Review their privacy policy to understand how they handle your data. Check features like JIT channels and notifications. Ensure they provide support to help when issues arise. Verify compatibility to confirm it works with your wallet choice.

The Future of LSPs

LSPs are evolving in several directions. More competition among multiple providers is improving options. Better standards are enabling growing interoperability. Hybrid models combine self-custody with optional LSP help. Decentralized LSPs are exploring federated or community models. Integration is seeing LSP services built into more apps. At the same time, many wallets have moved to so-called nodeless designs, built on systems like Spark or Liquid, where the user has no Lightning channel at all, and this changes the role LSPs play. The goal is to make Lightning as easy as Venmo without the custody tradeoffs.

In this lesson, we explored Lightning Service Providers — the businesses making Lightning accessible to mainstream users. Through innovations like JIT channels, LSPs remove friction and enable simple user experiences while users keep control of their own funds.

In our next lesson, we'll bring it all together and look at The Future of the Lightning Network — where Lightning is heading and what it might become.