{"type":"rich","version":"1.0","title":"Lloyd Fournier [ARCHIVE] wrote","author_name":"Lloyd Fournier [ARCHIVE] (npub1kh…y05yp)","author_url":"https://yabu.me/npub1khlhcuz0jrjwa0ayznq2q9agg4zvxfvx5x7jljrvwnpfzngrcf0q7y05yp","provider_name":"njump","provider_url":"https://yabu.me","html":"📅 Original date posted:2021-12-07\n📝 Original message:\nI was thinking along the same lines as Z. With MuSig2 and pre-sharing of\nsignature nonces it should stay three rounds and share a similar structure.\n\nOn Tue, 7 Dec 2021 at 11:08, ZmnSCPxj via Lightning-dev \u003c\nlightning-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e\n\u003e Basically, if my memory and understanding are accurate, in the above, it\n\u003e is the *PTLC-offerrer* which provides an adaptor signature.\n\u003e That adaptor signature would be included in the `update_add_ptlc` message.\n\u003e\n\nIsn't it the case that all previous PTLC adaptor signatures need to be\nre-sent for each update_add_ptlc message because the signatures would no\nlonger be valid once the commit tx changes. I think it's better to put it\nin `commitment_signed` if possible. This is what is done with pre-signed\nHTLC signatures at the moment anyway.\n\nLL\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20211207/894e2b77/attachment.html\u003e"}