<?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=PTLC</id>
	<title>PTLC - 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=PTLC"/>
	<link rel="alternate" type="text/html" href="https://en.bitcoin.it/w/index.php?title=PTLC&amp;action=history"/>
	<updated>2026-09-11T19:33:04Z</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=PTLC&amp;diff=71239&amp;oldid=prev</id>
		<title>NotATether: PTLC stub — point time locked contracts vs HTLC</title>
		<link rel="alternate" type="text/html" href="https://en.bitcoin.it/w/index.php?title=PTLC&amp;diff=71239&amp;oldid=prev"/>
		<updated>2026-09-09T13:45:32Z</updated>

		<summary type="html">&lt;p&gt;PTLC stub — point time locked contracts vs HTLC&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;Point Time Locked Contract&amp;#039;&amp;#039;&amp;#039; (&amp;#039;&amp;#039;&amp;#039;PTLC&amp;#039;&amp;#039;&amp;#039;) is a conditional payment that can be claimed by completing a Schnorr signature adaptor (equivalently, by revealing the discrete logarithm of a curve point), or refunded after a timeout. PTLCs are designed to replace hash time locked contracts (HTLCs) in [[Lightning Network]] routing and related atomic-swap style protocols so that hops do not share a single payment hash. As of 2026 they remain a design and implementation effort on top of Taproot-capable channels. They are not a completed BOLT that has replaced HTLCs on the public Lightning network.&lt;br /&gt;
&lt;br /&gt;
An HTLC locks coins to the preimage of a hash. Every hop of a routed Lightning payment typically uses the same hash, which can let observers correlate those hops. A PTLC instead locks to a curve point and unlocks via an adaptor signature. Per-hop blinding can give each intermediary a different point, so adjacent hops need not share a common lock value. On-chain, cooperative settlement can stay off chain as with HTLCs. A force-close under Taproot need not reveal a shared payment hash the way a HASH160 HTLC script can.&lt;br /&gt;
&lt;br /&gt;
Taproot and BIP340 made Schnorr adaptor constructions practical on Bitcoin. Lightning still routes with HTLCs because interoperable hops, invoices, and proof-of-payment flows are built around preimages. Mixed HTLC and PTLC paths would be needed during any transition.&lt;br /&gt;
&lt;br /&gt;
== See also ==&lt;br /&gt;
* [[Lightning Network]]&lt;br /&gt;
* [[Taproot]]&lt;br /&gt;
* [[MuSig]]&lt;br /&gt;
&lt;br /&gt;
== External links ==&lt;br /&gt;
* [https://bitcoinops.org/en/topics/ptlc/ Bitcoin Optech: PTLC]&lt;br /&gt;
* [https://github.com/bitcoin/bips/blob/master/bip-0340.mediawiki BIP340: Schnorr signatures for secp256k1]&lt;br /&gt;
* [https://download.wpsoftware.net/bitcoin/wizardry/mw-slides/2018-05-18-l2/slides.pdf Scriptless scripts slides (Poelstra)]&lt;br /&gt;
&lt;br /&gt;
[[Category:Technical]]&lt;br /&gt;
[[Category:Privacy]]&lt;/div&gt;</summary>
		<author><name>NotATether</name></author>
	</entry>
</feed>