Skip to content

Commit

Permalink
BOlT07: clarify dont_forward bit use cases. (#1198)
Browse files Browse the repository at this point in the history
  • Loading branch information
ziggie1984 authored Sep 18, 2024
1 parent e6ee5f8 commit 0809f77
Showing 1 changed file with 3 additions and 2 deletions.
5 changes: 3 additions & 2 deletions 07-routing-gossip.md
Original file line number Diff line number Diff line change
Expand Up @@ -452,8 +452,9 @@ or `node_id_2` otherwise.
The origin node:
- 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
channel peer, even though the channel has not yet been announced (i.e. the
`announce_channel` bit was not set).
channel peer, even though the channel has not yet been announced (i.e.
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
received from the peer, or the real channel `short_channel_id`.
- MUST set `dont_forward` to 1 in `message_flags`
Expand Down

0 comments on commit 0809f77

Please sign in to comment.