mirrors/lightning-bolts
1
0
Fork 0
mirror of https://github.com/lightning/bolts.git synced 2024-11-19 01:50:03 +01:00
Code Issues Projects Releases Wiki Activity

BOLT 4: rename onionmsg_hop to blinded_path_hop

Browse Source 
It's used for blinded payment paths, too, not just onion messages.

Suggested-by: @t-bast
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
This commit is contained in:
Rusty Russell 2024-07-17 10:56:32 +09:30
parent 43725d7f07
commit 6654c5711a
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
04-onion-routing.md
View File

@ -443,9 +443,9 @@ intermediary nodes could simply claim the remaining ones.
* [`point`:`first_node_id`] * [`point`:`first_node_id`]
* [`point`:`first_path_key`] * [`point`:`first_path_key`]
* [`byte`:`num_hops`] * [`byte`:`num_hops`]
* [`num_hops*onionmsg_hop`:`path`] * [`num_hops*blinded_path_hop`:`path`]
1. subtype: `onionmsg_hop` 1. subtype: `blinded_path_hop`
2. data: 2. data:
* [`point`:`blinded_node_id`] * [`point`:`blinded_node_id`]
* [`u16`:`enclen`] * [`u16`:`enclen`]
@ -503,7 +503,7 @@ The writer of a `blinded_path`:
- MUST set `first_path_key` to $`E_0`$ - MUST set `first_path_key` to $`E_0`$
- MUST create a series of blinded node IDs $`B_i`$ for each node using the following algorithm: - MUST create a series of blinded node IDs $`B_i`$ for each node using the following algorithm:
- $`B_i = HMAC256(\text{"blinded\_node\_id"}, ss_i) * N_i`$ (blinded `node_id` for $`N_i`$, private key known only by $`N_i`$) - $`B_i = HMAC256(\text{"blinded\_node\_id"}, ss_i) * N_i`$ (blinded `node_id` for $`N_i`$, private key known only by $`N_i`$)
- MUST set `blinded_node_id` for each `onionmsg_hop` in `path` to $`B_i`$ - MUST set `blinded_node_id` for each `blinded_path_hop` in `path` to $`B_i`$
- MAY replace $`E_{i+1}`$ with a different value, but if it does: - MAY replace $`E_{i+1}`$ with a different value, but if it does:
- MUST set `encrypted_data_tlv[i].next_path_key_override` to $`E_{i+1}`$ - MUST set `encrypted_data_tlv[i].next_path_key_override` to $`E_{i+1}`$
- MAY store private data in `encrypted_data_tlv[r].path_id` to verify that the route is used in the right context and was created by them - MAY store private data in `encrypted_data_tlv[r].path_id` to verify that the route is used in the right context and was created by them