<oembed><type>rich</type><version>1.0</version><title>ZmnSCPxj [ARCHIVE] wrote</title><author_name>ZmnSCPxj [ARCHIVE] (npub1g5…3ms3l)</author_name><author_url>https://yabu.me/npub1g5zswf6y48f7fy90jf3tlcuwdmjn8znhzaa4vkmtxaeskca8hpss23ms3l</author_url><provider_name>njump</provider_name><provider_url>https://yabu.me</provider_url><html>📅 Original date posted:2021-12-07&#xA;📝 Original message:&#xA;Good morning LL, and t-bast,&#xA;&#xA;&gt; &gt; Basically, if my memory and understanding are accurate, in the above, it is the *PTLC-offerrer* which provides an adaptor signature.&#xA;&gt; &gt; That adaptor signature would be included in the `update_add_ptlc` message.&#xA;&gt;&#xA;&gt; Isn&#39;t it the case that all previous PTLC adaptor signatures need to be re-sent for each update_add_ptlc message because the signatures would no longer be valid once the commit tx changes. I think it&#39;s better to put it in `commitment_signed` if possible. This is what is done with pre-signed HTLC signatures at the moment anyway.&#xA;&#xA;Agreed.&#xA;&#xA;This is also avoided by fast-forwards, BTW, simply because fast-forwards delay the change of the commitment tx.&#xA;It is another reason to consider fast-forwards, too....&#xA;&#xA;Regards,&#xA;ZmnSCPxj</html></oembed>