Lightning Service Provider (LSP)

A Lightning Service Provider (LSP) is a business or node operator that helps users connect to and transact on the Lightning Network, primarily by solving the inbound-liquidity problem. A brand-new Lightning wallet has no channels, and until someone opens a channel toward it, it cannot receive a single satoshi. An LSP opens that channel — often automatically and within seconds — so a new user can start receiving payments immediately instead of first learning channel management, capital allocation, and peer selection.

Inbound liquidity and JIT channels

Receiving on Lightning requires inbound capacity: bitcoin sitting on the remote side of a channel pointed at you. LSPs provision that capacity on demand. The most elegant model is the just-in-time (JIT) channel: the LSP sees an incoming payment destined for a user with no channels, opens a channel in direct response to it, and deducts the channel-open cost from that first payment. The user's experience is simply "I received money," with the plumbing handled behind the scenes. Other models let a user purchase a channel of a chosen size and duration up front, which suits merchants who know roughly how much they expect to receive. To make onboarding instant rather than waiting for on-chain confirmation, LSPs frequently pair JIT opens with a zero-conf channel, accepting a short window of trust in exchange for immediacy.

Standardization through bLIPs

Early LSPs each spoke their own API, which locked wallets to a single provider. The ecosystem has since converged on open specifications published as Bitcoin Lightning Improvement Proposals (bLIPs): bLIP-51 (LSPS1) defines ordering a channel from an LSP, bLIP-52 (LSPS2) defines JIT channels, and bLIP-50 (LSPS0) defines the underlying JSON-RPC transport carried over encrypted peer-to-peer messages. Standardized flows mean a wallet can shop among competing LSPs on price and reliability rather than being captive to one, which keeps the market honest.

The sovereignty trade-off

An LSP is a convenience layer, and every convenience layer deserves a clear-eyed look at what you are trusting. With a non-custodial LSP, your keys and your balance remain yours — the provider supplies liquidity and routing, not custody — but it does gain some visibility into your payment activity and some influence over your connectivity. If your only channel runs through one LSP, that LSP going offline takes your receiving ability with it. The mitigations are the usual ones: choose wallets built on open LSP specs, keep the ability to open your own channels as you grow, and treat the LSP as a bootstrap rather than a permanent dependency. This mirrors the broader pattern of self-custody: use service providers where they save you real work, but keep the exit door open.

Why miners and node runners should care

For a home miner or node runner, LSPs matter in two directions. First, they are the reason Lightning wallets now work out of the box for the people you orange-pill — receiving works on day one. Second, if you run a well-capitalized routing node, the LSP specifications describe a business you can participate in: selling inbound capacity is one of the few ways a node earns a return on deployed liquidity. Either way, understanding what an LSP does — and what it cannot do, because it never holds your keys — is basic literacy for operating on Lightning.