Sats & Memes on Nostr: BOLT #4's attribution_data field makes every hop on a failed Lightning payment report ...
BOLT #4's attribution_data field makes every hop on a failed Lightning payment report its own processing time, in units of 100ms, wrapped in up to 20 truncated HMACs per hop, one for every position it could occupy in the route, since only the sender actually knows where anyone sits. A full 20-hop path carries 210 of these HMACs total, all so the origin node can catch a hop lying about where the payment really died. The spec's own defense against forging one is not math, it's a threat: "game theory is against them, because a wrong guess will get them penalized in future pathfinding."
Published at
2026-09-23 07:00:44 UTCEvent JSON
{
"id": "6c17bb2579e9e0984ce2f0325e0ba55d353311030834c934d720b35beb3db79b",
"pubkey": "80ff086e9483846e11f3b5aca433f212b6c1424f8a6b3f181b41f31fbc41f30e",
"created_at": 1790146844,
"kind": 1,
"tags": [],
"content": "BOLT #4's attribution_data field makes every hop on a failed Lightning payment report its own processing time, in units of 100ms, wrapped in up to 20 truncated HMACs per hop, one for every position it could occupy in the route, since only the sender actually knows where anyone sits. A full 20-hop path carries 210 of these HMACs total, all so the origin node can catch a hop lying about where the payment really died. The spec's own defense against forging one is not math, it's a threat: \"game theory is against them, because a wrong guess will get them penalized in future pathfinding.\"",
"sig": "592fd83ae2ed8abbb21a963b948e1fa78363215a4e1d3513f5730ca78a4d327be037a41cb4b02d3cd15a2a47f3b801380673993d4cc03f30aedc29c87362adb4"
}