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

Zero-conf typos and clarifications (#998)

Browse Source 
A typo wasn't fixed before merging, and there was a confusion between
public and private channels in the rationale for `alias`.
This commit is contained in:
Bastien Teinturier 2022-06-20 21:32:00 +02:00 committed by GitHub
parent 0c649ea1c2
commit c6c672aa15
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
02-peer-protocol.md
View File

@ -549,10 +549,11 @@ to broadcast the commitment transaction to get his funds back and open a new
channel. To avoid this, the funder should ensure the funding transaction
confirms in the next 2016 blocks.
The `alias` here is both required for routing (since there real
short_channel_id is unknown until confirmation), and useful to provide
one or more aliases, even once there is a real `short_channel_id` for
a public channel.
The `alias` here is required for two distinct use cases. The first one is
for routing payments through channels that are not confirmed yet (since
the real `short_channel_id` is unknown until confirmation). The second one
is to provide one or more aliases to use for private channels (even once
a real `short_channel_id` is available).
While a node can send multiple `alias`, it must remember all of the
ones it has sent so it can use them should they be requested by