š
Original date posted:2021-12-07
š Original message:
Good morning LL, and t-bast,
> > Basically, if my memory and understanding are accurate, in the above, it is the *PTLC-offerrer* which provides an adaptor signature.
> > That adaptor signature would be included in the `update_add_ptlc` message.
>
> Isn'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's better to put it in `commitment_signed` if possible. This is what is done with pre-signed HTLC signatures at the moment anyway.
Agreed.
This is also avoided by fast-forwards, BTW, simply because fast-forwards delay the change of the commitment tx.
It is another reason to consider fast-forwards, too....
Regards,
ZmnSCPxj
ZmnSCPxj [ARCHIVE] /
npub1g5ā¦3ms3l
2023-06-09 13:04:37
in reply to nevent1qā¦7tcl
Author Public Key
npub1g5zswf6y48f7fy90jf3tlcuwdmjn8znhzaa4vkmtxaeskca8hpss23ms3lPublished at
2023-06-09 13:04:37Event JSON
{
"id": "3e18c87858a4aaae7b3d25bcef5bc2db239e41a3f748a33911aa3e855fbf0741",
"pubkey": "4505072744a9d3e490af9262bfe38e6ee5338a77177b565b6b37730b63a7b861",
"created_at": 1686315877,
"kind": 1,
"tags": [
[
"e",
"86d882af7142eecbdb4ce698181b82aaa475c9b46541e1e4831400616b496e77",
"",
"root"
],
[
"e",
"f40af67af32d0d84df5e2ddb1c6b037e0a3e311ce282b3e3f01f23fccf9e71e7",
"",
"reply"
],
[
"p",
"b5ff7c704f90e4eebfa414c0a017a84544c32586a1bd2fc86c74c2914d03c25e"
]
],
"content": "š
Original date posted:2021-12-07\nš Original message:\nGood morning LL, and t-bast,\n\n\u003e \u003e Basically, if my memory and understanding are accurate, in the above, it is the *PTLC-offerrer* which provides an adaptor signature.\n\u003e \u003e That adaptor signature would be included in the `update_add_ptlc` message.\n\u003e\n\u003e Isn'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's better to put it in `commitment_signed` if possible. This is what is done with pre-signed HTLC signatures at the moment anyway.\n\nAgreed.\n\nThis is also avoided by fast-forwards, BTW, simply because fast-forwards delay the change of the commitment tx.\nIt is another reason to consider fast-forwards, too....\n\nRegards,\nZmnSCPxj",
"sig": "ba6aaac28beb4b56e8b039f8b4a227979b39cd63d1453ec7a59ba27ef950df07dca3853ce3f6403f735baa5936c4c5ba68b19b159724c2694d5e0725fdf07eb2"
}