lnd/record
bitromortac 4fd4289a08
htlcswitch/hop: decode next_node_id blinded hops
Some implementations (e.g. Core Lightning) identify the next hop in a
blinded route by the next node's ID (next_node_id) instead of a short
channel ID. Decode such a hop into a node-ID next hop, the Right of
ForwardingInfo.NextHop, holding the next node's public key. The switch
resolves that key to one of our channels with the peer in a later commit.

BOLT 4 requires a non-final blinded hop to carry exactly one of
short_channel_id or next_node_id, so a hop that sets both is rejected.
2026-07-30 08:54:35 +00:00
..
amp.go multi: Fix final hop payload size for AMP payments. 2024-02-03 12:16:06 +00:00
blinded_data.go htlcswitch/hop: decode next_node_id blinded hops 2026-07-30 08:54:35 +00:00
blinded_data_test.go lint: remove redundant loop var copies in test files 2026-06-03 15:32:45 -03:00
custom_records.go multi: make validation for keysend stricter 2025-03-25 04:42:03 -05:00
custom_records_test.go record: add unit test 2025-03-25 10:36:16 -05:00
experimental.go multi: rename key_send, key-send and key send to keysend 2020-01-16 18:37:16 -08:00
hop.go multi: actor-based onion message forwarding 2026-03-02 15:46:21 +01:00
mpp.go multi: formatting and comment fixes 2022-02-10 11:02:02 +01:00
record_test.go lint: remove redundant loop var copies in test files 2026-06-03 15:32:45 -03:00