📅 Original date posted:2015-08-24
📝 Original message:
Anthony Towns <aj at erisian.com.au> writes:
> On 24 August 2015 at 02:59, Rusty Russell <rusty at rustcorp.com.au> wrote:
>> 2) Dave starts the HTLC process, but then times out (doesn't resolve
>> HTLC in 20*11 seconds, and doesn't send back a blame
>> packet from Emma, either).
>> In the latter case, Carol dumps the commit tx to the blockchain, and the
>> screwed-up HTLC (and any other casualty HTLCs in progress, sorry). She
>> can include this commit tx + htlc txs in the blame packet back to Bob;
>> there's no reason to name Dave AFAICT[1].
>
> The HTLC txn provides Dave's public key id though (assuming you un-P2SH
> it, which you need to to prove that it corresponds with the R you expect),
> which is the only name for Dave that matters, isn't it?
There's no reason for the two to be connected. You have a pubkey as
your ID for network and routing encryption, but you can offer any
transaction as an anchor, and use any keys you want.
Now, Joseph was suggested that it doesn't *have* to be this way, such
that the blockchain would show all the channels open, but while that's a
cute hack I don't think it's necessary.
Cheers,
Rusty.
Rusty Russell [ARCHIVE] /
npub1zw…hkhpx
2023-06-09 12:44:06
in reply to nevent1q…d083
Author Public Key
npub1zw7cc8z78v6s3grujfvcv3ckpvg6kr0w7nz9yzvwyglyg0qu5sjsqhkhpxPublished at
2023-06-09 12:44:06Event JSON
{
"id": "58bee3359fa17fab1c91dacd7e6c6f9f361a271fd4d246fa73b9e9374e319d07",
"pubkey": "13bd8c1c5e3b3508a07c92598647160b11ab0deef4c452098e223e443c1ca425",
"created_at": 1686314646,
"kind": 1,
"tags": [
[
"e",
"a92f734d740b85399f0e70711c3ef451f97eec2048c08c21ef8e0700fe174d1c",
"",
"root"
],
[
"e",
"ab3a48e34dd598662fc676a36577058ba23a30859fe3da27e0aeb8ec0c4df5ed",
"",
"reply"
],
[
"p",
"f0feda6ad58ea9f486e469f87b3b9996494363a26982b864667c5d8acb0542ab"
]
],
"content": "📅 Original date posted:2015-08-24\n📝 Original message:\nAnthony Towns \u003caj at erisian.com.au\u003e writes:\n\u003e On 24 August 2015 at 02:59, Rusty Russell \u003crusty at rustcorp.com.au\u003e wrote:\n\u003e\u003e 2) Dave starts the HTLC process, but then times out (doesn't resolve\n\u003e\u003e HTLC in 20*11 seconds, and doesn't send back a blame\n\u003e\u003e packet from Emma, either).\n\u003e\u003e In the latter case, Carol dumps the commit tx to the blockchain, and the\n\u003e\u003e screwed-up HTLC (and any other casualty HTLCs in progress, sorry). She\n\u003e\u003e can include this commit tx + htlc txs in the blame packet back to Bob;\n\u003e\u003e there's no reason to name Dave AFAICT[1].\n\u003e\n\u003e The HTLC txn provides Dave's public key id though (assuming you un-P2SH\n\u003e it, which you need to to prove that it corresponds with the R you expect),\n\u003e which is the only name for Dave that matters, isn't it?\n\nThere's no reason for the two to be connected. You have a pubkey as\nyour ID for network and routing encryption, but you can offer any\ntransaction as an anchor, and use any keys you want.\n\nNow, Joseph was suggested that it doesn't *have* to be this way, such\nthat the blockchain would show all the channels open, but while that's a\ncute hack I don't think it's necessary.\n\nCheers,\nRusty.",
"sig": "15f6e0cdbd2d5e1a9b923bbd5cef7c128fea49b67456d6af24d60c8c209ca5f5c4dd6beaf0067b6f970fdb8f88c246b3a3af8118983d554e3d04110d1b1c8995"
}