<?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=Just-in-time_channel</id>
	<title>Just-in-time channel - 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=Just-in-time_channel"/>
	<link rel="alternate" type="text/html" href="https://en.bitcoin.it/w/index.php?title=Just-in-time_channel&amp;action=history"/>
	<updated>2026-09-12T06:15:12Z</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=Just-in-time_channel&amp;diff=71251&amp;oldid=prev</id>
		<title>NotATether: Create Just-in-time channel stub (LSP / LSPS2 JIT open)</title>
		<link rel="alternate" type="text/html" href="https://en.bitcoin.it/w/index.php?title=Just-in-time_channel&amp;diff=71251&amp;oldid=prev"/>
		<updated>2026-09-12T03:16:32Z</updated>

		<summary type="html">&lt;p&gt;Create Just-in-time channel stub (LSP / LSPS2 JIT open)&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;just-in-time channel&amp;#039;&amp;#039;&amp;#039; (JIT channel) is a [[Lightning Network]] channel that a Lightning service provider (LSP) opens in response to an incoming payment for a client that does not yet have inbound capacity. The LSP holds the first payment, funds a new channel, then forwards the HTLC into that channel so a new user can receive without first opening a channel or buying inbound liquidity.&lt;br /&gt;
&lt;br /&gt;
JIT channels should not be confused with just-in-time routing, which rebalances existing channels so a payment that would otherwise fail for lack of local liquidity can be accepted.&lt;br /&gt;
&lt;br /&gt;
Receiving on Lightning needs inbound capacity: a channel where the remote side holds enough balance (and a free HTLC slot) to carry the payment. A new wallet has neither. A JIT open treats the incoming payment as the event that creates the channel. Negotiation is commonly specified by LSPS2 (bLIP-52). The open usually depends on zero-confirmation channel features (&amp;lt;code&amp;gt;option_zeroconf&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;option_scid_alias&amp;lt;/code&amp;gt;) so peers can use a short-channel-id alias before the funding transaction confirms. See also [[Zero-confirmation transaction]].&lt;br /&gt;
&lt;br /&gt;
In outline: the client gets JIT parameters from an LSP and embeds a reserved SCID in invoice routing hints. When a matching payment arrives, the LSP holds the HTLC, opens an often-unannounced channel with the client, funds it (crediting the payment minus any opening fee), and forwards the HTLC so the client can settle with the preimage. Without extra on-chain contracts, the first open typically requires trusting the LSP for that handshake. After a channel exists, later capacity changes are often done with [[Splicing]] rather than more JIT opens. Related liquidity tooling includes [[Dual funding]].&lt;br /&gt;
&lt;br /&gt;
== See also ==&lt;br /&gt;
* [[Lightning Network]]&lt;br /&gt;
* [[Dual funding]]&lt;br /&gt;
* [[Splicing]]&lt;br /&gt;
* [[Zero-confirmation transaction]]&lt;br /&gt;
&lt;br /&gt;
== External links ==&lt;br /&gt;
* [https://bitcoinops.org/en/topics/jit-channels/ Bitcoin Optech: Just-In-Time (JIT) channels]&lt;br /&gt;
* [https://github.com/BitcoinAndLightningLayerSpecs/lsp Lightning Service Provider specifications (incl. LSPS2)]&lt;br /&gt;
&lt;br /&gt;
[[Category:Technical]]&lt;/div&gt;</summary>
		<author><name>NotATether</name></author>
	</entry>
</feed>