<oembed><type>rich</type><version>1.0</version><title>Lloyd Fournier [ARCHIVE] wrote</title><author_name>Lloyd Fournier [ARCHIVE] (npub1kh…y05yp)</author_name><author_url>https://yabu.me/npub1khlhcuz0jrjwa0ayznq2q9agg4zvxfvx5x7jljrvwnpfzngrcf0q7y05yp</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;I was thinking along the same lines as Z. With MuSig2 and pre-sharing of&#xA;signature nonces it should stay three rounds and share a similar structure.&#xA;&#xA;On Tue, 7 Dec 2021 at 11:08, ZmnSCPxj via Lightning-dev &lt;&#xA;lightning-dev at lists.linuxfoundation.org&gt; wrote:&#xA;&#xA;&gt;&#xA;&gt; Basically, if my memory and understanding are accurate, in the above, it&#xA;&gt; is the *PTLC-offerrer* which provides an adaptor signature.&#xA;&gt; That adaptor signature would be included in the `update_add_ptlc` message.&#xA;&gt;&#xA;&#xA;Isn&#39;t it the case that all previous PTLC adaptor signatures need to be&#xA;re-sent for each update_add_ptlc message because the signatures would no&#xA;longer be valid once the commit tx changes. I think it&#39;s better to put it&#xA;in `commitment_signed` if possible. This is what is done with pre-signed&#xA;HTLC signatures at the moment anyway.&#xA;&#xA;LL&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20211207/894e2b77/attachment.html&gt;</html></oembed>