Joost Jager [ARCHIVE] on Nostr: 📅 Original date posted:2021-04-24 📝 Original message: > > But Joost pointed out ...
Published at
2023-06-09 12:40:01Event JSON
{
"id": "8909abf809afc57098b4c1cc7c77a0d2ae8dd68282a232ab7910fe90780068c9",
"pubkey": "ec3fb08b335b94aace30d13181f2ad0280df9bc34f1a99832c4e2da8fb125eb3",
"created_at": 1686314401,
"kind": 1,
"tags": [
[
"e",
"ce3991df6426414fa320848d6dd03482b16a02969188461536ebec29085fe0f2",
"",
"root"
],
[
"e",
"1fd66ff9ac63b3baba740687255740127a9df457abc8048d229c254687eabb63",
"",
"reply"
],
[
"p",
"13bd8c1c5e3b3508a07c92598647160b11ab0deef4c452098e223e443c1ca425"
]
],
"content": "📅 Original date posted:2021-04-24\n📝 Original message:\n\u003e\n\u003e But Joost pointed out that you need to know the node_id of the next node\n\u003e though: this isn't quite true, since if the node_id is wrong the spec\n\u003e says you should send an `update_fail_malformed_htlc` with failure code\n\u003e invalid_onion_hmac, which node N turns into its own failure message.\n\u003e Perhaps it should convert it to `unknown_next_peer` instead? This isn't\n\u003e a common error on the modern network; I think our onion implementations\n\u003e have been rock solid.\n\u003e\n\nIsn't this what I am suggesting here?\nhttps://twitter.com/joostjgr/status/1385150318959341569\n\nJoost\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20210424/583bf0c4/attachment-0001.html\u003e",
"sig": "bebb407e979d49def506f9ba6b3da022a14e6d8129643dc423900f22573b763b4ac5fc1b39ad23022e58775e103ffe607f81705b9f46139d0c082b340e5c13d7"
}