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

BOLT 11: fix formatting typo, r length value, and channel_id->short_channel_id (#212)

Browse Source 
* BOLT 11: fix formatting typo, and `r` length value.

The r field is 408 bytes long, which is 82 characters encoded;
this should have been updated when the fee and cltv sizes were
updated (prior to merge into repo).

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

* BOLT 11: `channel_id`->`short_channel_id`
This commit is contained in:
Pierre-Marie Padiou 2017-07-24 10:26:49 +02:00 committed by GitHub
parent 80688d7900
commit df66a4e85a
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
11-payment-encoding.md
View File

@ -105,7 +105,7 @@ Currently defined Tagged Fields are:
* `r` (3): extra routing information. This should be appended to the route
to allow routing to non-public nodes; there may be more than one of these.
* `pubkey` (264 bits)
* `channel_id` (64 bits)
* `short_channel_id` (64 bits)
* `fee` (64 bits, big-endian)
* `cltv_expiry_delta` (16 bits, big-endian)
@ -133,7 +133,7 @@ a public key hash, or `18` followed by a script hash.
A writer MUST include at least one `r` field if it does not have a
public channel associated with its public key. The `pubkey` is the
node ID of the start of the channel, `channel_id` is the channel ID
node ID of the start of the channel, `short_channel_id` is the short channel ID
field to identify the channel, `fee` is the total fee required to use
that channel to send `amount` to the final node, specified in 10^-11
currency units, and `cltv_expiry_delta` is the block delta required
@ -147,8 +147,8 @@ the most-preferred field first, followed by less-preferred fields in
order.
A reader MUST skip over unknown fields, an `f` field with unknown
`version`, or a `p`, `h`, `n` or `r` field which does not have ``data_length`` 52,
52, 53 or 79 respectively.
`version`, or a `p`, `h`, `n` or `r` field which does not have `data_length` 52,
52, 53 or 82 respectively.
A reader MUST check that the SHA-2 256 in the `h` field exactly
matches the hashed description.
@ -310,7 +310,7 @@ Breakdown:
* `p`: payment preimage...
* `r`: tagged field: route information
* `zj`: `data_length` (`z` = 2, `j` = 18. 2 * 32 + 18 = 82)
`q20q82gphp2nflc7jtzrcazrra7wwgzxqc8u7754cdlpfrmccae92qgzqvzq2ps8pqqqqqqqqqqqq9qqqv`: pubkey `029e03a901b85534ff1e92c43c74431f7ce72046060fcf7a95c37e148f78c77255`, `channel_id` 0102030405060708, `fee` 20 millisatoshi, `cltv_expiry_delta` 3.
`q20q82gphp2nflc7jtzrcazrra7wwgzxqc8u7754cdlpfrmccae92qgzqvzq2ps8pqqqqqqqqqqqq9qqqv`: pubkey `029e03a901b85534ff1e92c43c74431f7ce72046060fcf7a95c37e148f78c77255`, `short_channel_id` 0102030405060708, `fee` 20 millisatoshi, `cltv_expiry_delta` 3.
* `f`: tagged field: fallback address...
* `h`: tagged field: hash of description...
* `jtf8rrkd7dujvdvrxhuk5a0tt9x9qh0t95jemn4tpen9y3nn7yt8jrmlyzffjh0hue8edkkq3090hruc8shpfu6wk4chfdvdusakycgp`: signature