Skip to content

BOLT 7: clarify how to encode multiple reply_channel_range messages #730

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
sstone wants to merge 1 commit into from
Closed

BOLT 7: clarify how to encode multiple reply_channel_range messages #730

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions 07-routing-gossip.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down