From ba0040b8be1cd0f4f5b3b0d74e982dc75300dec6 Mon Sep 17 00:00:00 2001 From: John Newbery Date: Tue, 24 Mar 2020 10:02:02 -0400 Subject: [PATCH 1/2] Bolt #7: Update introduction text 'three gossip messages' should refer to node and channel discovery messages, not just channel discovery messages. --- 07-routing-gossip.md | 22 ++++++++++++---------- 1 file changed, 12 insertions(+), 10 deletions(-) diff --git a/07-routing-gossip.md b/07-routing-gossip.md index 1200ab698..b84c55d60 100644 --- a/07-routing-gossip.md +++ b/07-routing-gossip.md @@ -7,16 +7,18 @@ Node and channel discovery serve two different purposes: - Channel discovery allows the creation and maintenance of a local view of the network's topology, so that a node can discover routes to desired destinations. - Node discovery allows nodes to broadcast their ID, host, and port, so that other nodes can open connections and establish payment channels with them. -To support channel discovery, three *gossip messages* are supported. Peers in the network exchange -`channel_announcement` messages containing information regarding new -channels between the two nodes. They can also exchange `channel_update` -messages, which update information about a channel. There can only be -one valid `channel_announcement` for any channel, but at least two -`channel_update` messages are expected. - -To support node discovery, peers exchange `node_announcement` -messages, which supply additional information about the nodes. There may be -multiple `node_announcement` messages, in order to update the node information. +To support channel and node discovery, three *gossip messages* are supported: + + - For channel discovery, peers in the network exchange + `channel_announcement` messages containing information regarding new + channels between the two nodes. They can also exchange `channel_update` + messages, which update information about a channel. There can only be + one valid `channel_announcement` for any channel, but at least two + `channel_update` messages are expected. + +- For node discovery, peers exchange `node_announcement` + messages, which supply additional information about the nodes. There may be + multiple `node_announcement` messages, in order to update the node information. # Table of Contents From a523085e8823472b59bc8fac64fbfe1b443d2fa6 Mon Sep 17 00:00:00 2001 From: John Newbery Date: Tue, 24 Mar 2020 10:05:13 -0400 Subject: [PATCH 2/2] Bolt #7: Maintain node discovery/channel discovery ordering The introductory paragraph describes node discovery and channel discovery, but changes the ordering. Keep the same ordering throughout the paragraph for readability. --- 07-routing-gossip.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/07-routing-gossip.md b/07-routing-gossip.md index b84c55d60..06db1ba8a 100644 --- a/07-routing-gossip.md +++ b/07-routing-gossip.md @@ -4,11 +4,15 @@ This specification describes simple node discovery, channel discovery, and chann Node and channel discovery serve two different purposes: - - Channel discovery allows the creation and maintenance of a local view of the network's topology, so that a node can discover routes to desired destinations. - Node discovery allows nodes to broadcast their ID, host, and port, so that other nodes can open connections and establish payment channels with them. + - Channel discovery allows the creation and maintenance of a local view of the network's topology, so that a node can discover routes to desired destinations. To support channel and node discovery, three *gossip messages* are supported: +- For node discovery, peers exchange `node_announcement` + messages, which supply additional information about the nodes. There may be + multiple `node_announcement` messages, in order to update the node information. + - For channel discovery, peers in the network exchange `channel_announcement` messages containing information regarding new channels between the two nodes. They can also exchange `channel_update` @@ -16,10 +20,6 @@ To support channel and node discovery, three *gossip messages* are supported: one valid `channel_announcement` for any channel, but at least two `channel_update` messages are expected. -- For node discovery, peers exchange `node_announcement` - messages, which supply additional information about the nodes. There may be - multiple `node_announcement` messages, in order to update the node information. - # Table of Contents * [Definition of `short_channel_id`](#definition-of-short_channel_id)