mirrors/lightning-bolts
1
0
Fork 0
mirror of https://github.com/lightning/bolts.git synced 2025-02-23 22:46:57 +01:00
Code Issues Projects Releases Wiki Activity

BOLT 4: channel_id -> short_channel_id

Browse source 
Consistency with BOLT 7 makes this much clearer.

Closes: #195
Reported-by: https://github.com/nayuta-ueno
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
This commit is contained in:
Rusty Russell 2017-06-30 15:12:02 +09:30
parent b574c18f24
commit 365a5a0f9f
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

@ -109,7 +109,7 @@ only `realm` 0 is defined, and for that, the `per_hop` format is:
1. type: `per_hop` (for `realm` 0)
2. data:
* [`8`:`channel_id`]
* [`8`:`short_channel_id`]
* [`8`:`amt_to_forward`]
* [`4`:`outgoing_cltv_value`]
* [`12`:`padding`]
@ -125,7 +125,7 @@ the values as specified within the `per_hop`.
Field Description:
* `channel_id` - The channel used to route the message, which implies the
* `short_channel_id` - The channel used to route the message, which implies the
next hop is the other end of the channel.
* `amt_to_forward` - The amount in milli-satoshi to forward to the next
@ -221,7 +221,7 @@ following operations:
- It generates a _rho_-key and _mu_-key using the hop's shared secret.
- The `hops_data` field is right-shifted by 65 bytes, discarding the last 65 bytes that exceed the 1300 bytes.
The `version`, `channel_id`, `amt_to_forward`, `outgoing_cltv_value`, `padding` and `HMAC` are copied into
The `version`, `short_channel_id`, `amt_to_forward`, `outgoing_cltv_value`, `padding` and `HMAC` are copied into
the following 65 bytes.
The _rho_-key is used to generate 1300 bytes of pseudo-random byte stream and applied with `XOR` to the `hops_data` field.
Should this be the last hop, i.e., the first iteration, then the tail of the `hops_data` field is overwritten with the routing info `filler`.