From 604f010afbe42804b03870b2de23ea73eb0820e9 Mon Sep 17 00:00:00 2001 From: sstone Date: Mon, 20 Jan 2020 10:52:56 +0100 Subject: [PATCH] BOLT 7: clarify how to encode multiple `reply_channel_range` messages When multiple `reply_channel_range` messages are sent back for a single `query_channel_range` query, they must cover the requested block range without gaps or overlaps: `first_blocknum` must be set to the previous `reply_channel_range`'s `first_blocknum` plus `number_of_blocks`. --- 07-routing-gossip.md | 1 + 1 file changed, 1 insertion(+) diff --git a/07-routing-gossip.md b/07-routing-gossip.md index 6ae579d8a..ffa68d268 100644 --- a/07-routing-gossip.md +++ b/07-routing-gossip.md @@ -783,6 +783,7 @@ The receiver of `query_channel_range`: - MUST encode a `short_channel_id` for every open channel it knows in blocks `first_blocknum` to `first_blocknum` plus `number_of_blocks` minus one. - MUST limit `number_of_blocks` to the maximum number of blocks whose results could fit in `encoded_short_ids` + - MUST set `first_blocknum` to the previous `reply_channel_range`'s `first_blocknum` plus `number_of_blocks` when sending back multiple replies for the same `query_channel_range` request. - if does not maintain up-to-date channel information for `chain_hash`: - MUST set `complete` to 0. - otherwise: