From f5e60e0c6bacd6c51b58b064634e3911b5579c74 Mon Sep 17 00:00:00 2001 From: Conner Fromknecht Date: Mon, 15 Jul 2019 13:59:33 -0700 Subject: [PATCH] BOLT07: don't send historical updates for gossip_timestamp_filter This commit removes the suggestion for nodes to respond with all known updates that satisfy the timestamps of a gossip_timestamp_filter message. This behavior is identical to using the `initial_routing_sync`, which has been deprecated due to the inefficient nature of sending the entire graph on every connection. Now, the requirements simply say that only new messages should be sent to peers. Given the upcoming addition of `extended_gossip_queries`, implementations should use this feature to locate missing graph information instead of relying the on the remote peer to dump everything. --- 07-routing-gossip.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/07-routing-gossip.md b/07-routing-gossip.md index 769e5a9a4..0be1a14d7 100644 --- a/07-routing-gossip.md +++ b/07-routing-gossip.md @@ -698,10 +698,6 @@ The sender: that it wants the gossip to refer to. The receiver: - - SHOULD send all gossip messages whose `timestamp` is greater or - equal to `first_timestamp`, and less than `first_timestamp` plus - `timestamp_range`. - - MAY wait for the next outgoing gossip flush to send these. - SHOULD restrict future gossip messages to those whose `timestamp` is greater or equal to `first_timestamp`, and less than `first_timestamp` plus `timestamp_range`.