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

BOlT07: clarify dont_forward bit use cases. (#1198)

Browse Source
This commit is contained in:
ziggieXXX 2024-09-18 13:37:56 +02:00 committed by GitHub
parent e6ee5f8b95
commit 0809f77c7b
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
07-routing-gossip.md
View File

@ -452,8 +452,9 @@ or `node_id_2` otherwise.
The origin node: The origin node:
- MUST NOT send a created `channel_update` before `channel_ready` has been received. - MUST NOT send a created `channel_update` before `channel_ready` has been received.
- MAY create a `channel_update` to communicate the channel parameters to the - MAY create a `channel_update` to communicate the channel parameters to the
channel peer, even though the channel has not yet been announced (i.e. the channel peer, even though the channel has not yet been announced (i.e.
`announce_channel` bit was not set). the `announce_channel` bit was not set or the `channel_update` is sent before
the peers exchanged [announcement signatures](#the-announcement_signatures-message)).
- MUST set the `short_channel_id` to either an `alias` it has - MUST set the `short_channel_id` to either an `alias` it has
received from the peer, or the real channel `short_channel_id`. received from the peer, or the real channel `short_channel_id`.
- MUST set `dont_forward` to 1 in `message_flags` - MUST set `dont_forward` to 1 in `message_flags`