From 0809f77c7b57abe138c02697f573b52b470fb647 Mon Sep 17 00:00:00 2001
From: ziggieXXX <90319354+ziggie1984@users.noreply.github.com>
Date: Wed, 18 Sep 2024 13:37:56 +0200
Subject: [PATCH] BOlT07: clarify dont_forward bit use cases. (#1198)

---
 07-routing-gossip.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/07-routing-gossip.md b/07-routing-gossip.md
index b341dd8..2235327 100644
--- a/07-routing-gossip.md
+++ b/07-routing-gossip.md
@@ -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`