Joost Jager [ARCHIVE] on Nostr: 📅 Original date posted:2021-04-24 📝 Original message: > > But Joost pointed out ...
Published at
2023-06-09 13:02:24Event JSON
{
"id": "bbaa44f0e8a437818afb297c131a13bb5494691dcab66a746ab4f78c82376406",
"pubkey": "ec3fb08b335b94aace30d13181f2ad0280df9bc34f1a99832c4e2da8fb125eb3",
"created_at": 1686315744,
"kind": 1,
"tags": [
[
"e",
"e74154b9d738dd3de8bd4bed8eec44a2d688e33c01fb8949a1636811c5f23fe8",
"",
"root"
],
[
"e",
"a1844e84dded7578fd03ce9f765d82e40e1e0da02f675bc5b8700169cebfa559",
"",
"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": "4ce946012740f22bbfac9c2e9a8c9e2c89fd8e6a316891dfdf50dabbbd98eb75bc08139eaab4ac8d4345d715693719883f01ed743cb25dcaa831da213c3a17f0"
}