From b5ce609697ef91b000f2a64a35c4b2220c6e4f31 Mon Sep 17 00:00:00 2001 From: Rusty Russell Date: Tue, 9 Apr 2024 05:48:17 +0930 Subject: [PATCH] BOLT 9: Remove initial_routing_sync. This only had an effect when `gossip_queries` was not negotiated, which is now assumed. Signed-off-by: Rusty Russell --- 07-routing-gossip.md | 10 ---------- 09-features.md | 5 ----- 2 files changed, 15 deletions(-) diff --git a/07-routing-gossip.md b/07-routing-gossip.md index fc9889da6..7999e5394 100644 --- a/07-routing-gossip.md +++ b/07-routing-gossip.md @@ -28,7 +28,6 @@ To support channel and node discovery, three *gossip messages* are supported: * [The `node_announcement` Message](#the-node_announcement-message) * [The `channel_update` Message](#the-channel_update-message) * [Query Messages](#query-messages) - * [Initial Sync](#initial-sync) * [Rebroadcasting](#rebroadcasting) * [HTLC Fees](#htlc-fees) * [Pruning the Network View](#pruning-the-network-view) @@ -894,15 +893,6 @@ first few peers, in the assumption that propagation is adequate). This assumption of adequate propagation does not apply for gossip messages generated directly by the node itself, so they should ignore filters. -## Initial Sync - -If a node requires an initial sync of gossip messages, it will be flagged -in the `init` message, via a feature flag ([BOLT #9](09-features.md#assigned-localfeatures-flags)). - -Note that the `initial_routing_sync` feature is overridden (and should -be considered equal to 0) by the `gossip_queries` feature if the -latter is negotiated via `init`. - ### Requirements A node: diff --git a/09-features.md b/09-features.md index 122ccd7f6..fa306270e 100644 --- a/09-features.md +++ b/09-features.md @@ -33,7 +33,6 @@ The Context column decodes as follows: | Bits | Name | Description | Context | Dependencies | Link | |-------|-----------------------------------|-----------------------------------------------------------|----------|---------------------------|-----------------------------------------------------------------------| | 0/1 | `option_data_loss_protect` | ASSUMED | | | | -| 3 | `initial_routing_sync` | Sending node needs a complete routing information dump | I | | [BOLT #7][bolt07-sync] | | 4/5 | `option_upfront_shutdown_script` | Commits to a shutdown scriptpubkey when opening channel | IN | | [BOLT #2][bolt02-open] | | 6/7 | `gossip_queries` | Peer has useful gossip to share | | | | | 8/9 | `var_onion_optin` | ASSUMED | | | | @@ -79,10 +78,6 @@ above can be found in [BOLT #1: The `init` Message](01-messaging.md#the-init-mes ## Rationale -There is no _even_ bit for `initial_routing_sync`, as there would be little -point: a local node can't determine if a remote node complies, and it must -interpret the flag, as defined in the initial spec. - Note that for feature flags which are available in both the `node_announcement` and [BOLT 11](11-payment-encoding.md) invoice contexts, the features as set in the [BOLT 11](11-payment-encoding.md) invoice should override those set in the