feat: fetch unknown blocks from peers#61
Merged
MegaRedHand merged 25 commits intomainfrom Jan 28, 2026
Merged
Conversation
libp2p::request_response expects protocols to be equivalent between them, and negotiates with the peer which one to use. Since we specified the status first in the list of protocols, it seems to default to that one when we send a request.
This reverts commit b4ffabd.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR makes the BlockchainServer actively fetch missing blocks from the P2P module. Whenever we try to process a block which we don't have the pre-state for, we instead send a message to the P2P event loop, which sends a request for that block to peers. If any of the requests fail, it keeps retrying it with a backoff mechanism.