<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://en.bitcoin.it/w/index.php?action=history&amp;feed=atom&amp;title=Lightning_service_provider</id>
	<title>Lightning service provider - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://en.bitcoin.it/w/index.php?action=history&amp;feed=atom&amp;title=Lightning_service_provider"/>
	<link rel="alternate" type="text/html" href="https://en.bitcoin.it/w/index.php?title=Lightning_service_provider&amp;action=history"/>
	<updated>2026-09-12T06:23:02Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.43.9</generator>
	<entry>
		<id>https://en.bitcoin.it/w/index.php?title=Lightning_service_provider&amp;diff=71260&amp;oldid=prev</id>
		<title>NotATether: Create Lightning service provider stub (LSPS / bLIPs)</title>
		<link rel="alternate" type="text/html" href="https://en.bitcoin.it/w/index.php?title=Lightning_service_provider&amp;diff=71260&amp;oldid=prev"/>
		<updated>2026-09-12T03:38:59Z</updated>

		<summary type="html">&lt;p&gt;Create Lightning service provider stub (LSPS / bLIPs)&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;A &amp;#039;&amp;#039;&amp;#039;Lightning service provider&amp;#039;&amp;#039;&amp;#039; (LSP) is a [[Lightning Network]] node operator that sells inbound liquidity and related services to wallets, most commonly by opening channels toward the wallet so the wallet can receive payments. The role is an application-layer business on top of the Lightning peer protocol, not a consensus change.&lt;br /&gt;
&lt;br /&gt;
A Lightning payment can only be received on a channel that already has bitcoin on the remote side (inbound capacity). A new wallet has no channels until some peer opens toward it or the wallet opens outbound and later receives. LSPs perform that operational work (on-chain fees, UTXO management, and staying online). Early providers each exposed a proprietary API. A common specification effort (originally LSPS) was later published as Bitcoin Lightning Improvement Proposals (bLIPs) in the lightning/blips repository.&lt;br /&gt;
&lt;br /&gt;
The LSP and the wallet are ordinary Lightning peers. Service requests ride on the encrypted BOLT 8 transport as JSON-RPC 2.0 payloads (message type 37913), defined as LSPS0 / bLIP 50. LSPS1 / bLIP 51 standardizes purchasing a channel (order, payment, open, refund on failure). LSPS2 / bLIP 52 standardizes [[Just-in-time channel]] opens: the LSP intercepts an incoming HTLC, opens toward the wallet (often zero-conf), and forwards the payment minus an opening fee. LSPS5 / bLIP 55 registers HTTPS webhooks so a usually offline mobile wallet can be notified of activity. Related tools for channel capacity include [[Dual funding]] and [[Splicing]]. An LSP is a liquidity counterparty, not a custodian of the wallet&amp;#039;s channel keys when the wallet holds them. Receiving still depends on the LSP&amp;#039;s willingness to extend inbound capacity and on the LSP&amp;#039;s own outbound routes. [[Watchtower]] services are a separate always-on watcher role; some hosts combine both functions.&lt;br /&gt;
&lt;br /&gt;
== See also ==&lt;br /&gt;
* [[Lightning Network]]&lt;br /&gt;
* [[Just-in-time channel]]&lt;br /&gt;
* [[Dual funding]]&lt;br /&gt;
* [[Splicing]]&lt;br /&gt;
* [[Watchtower]]&lt;br /&gt;
* [[LNURL]]&lt;br /&gt;
&lt;br /&gt;
== External links ==&lt;br /&gt;
* [https://github.com/lightning/blips Bitcoin Lightning Improvement Proposals (bLIPs)]&lt;br /&gt;
* [https://github.com/lightning/blips/blob/master/blip-0050.md bLIP 50 (LSPS0)]&lt;br /&gt;
* [https://github.com/lightning/blips/blob/master/blip-0051.md bLIP 51 (LSPS1)]&lt;br /&gt;
* [https://github.com/lightning/blips/blob/master/blip-0052.md bLIP 52 (LSPS2)]&lt;br /&gt;
* [https://bitcoinops.org/en/topics/jit-channels/ Bitcoin Optech: Just-In-Time (JIT) channels]&lt;br /&gt;
&lt;br /&gt;
[[Category:Technical]]&lt;/div&gt;</summary>
		<author><name>NotATether</name></author>
	</entry>
</feed>