Support for frontier requests in stateless bootstrap server #4337
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pwojcikdev
force-pushed
the
stateless-frontier-server
branch
from
941cd58
to
165cc91
Compare
clemahieu
approved these changes
Nov 30, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A missing piece for transitioning from legacy bootstrap to full ascending bootstrap was a missing frontier query. This query is needed for efficient (bulk) scanning of accounts for updates. Currently we are forced to do a request - reply for every single account that we want to check for changes. This PR adds a new payload type for ascending bootstrap messages and support for serving those requests in
bootstrap_server.frontier request:
frontier response:
This also bumps the current protocol version to 20, keeping compatibility with previous versions as is.