Skip to content
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.

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

Add CurrentBlockHeaderRequest{} #16

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

IronGauntlets
Copy link
Collaborator

The response to CurrentBlockHeaderRequest{} is the peer's local current header. This can be used to get a rough idea of what the latest block is as viewed by other peers on the network. The header can be compared with a subset of peers to determine an efficient way of pulling blocks from the network while syncing.

Initially, we modified the iteration message to include a latest option, however, since the iteration message is shared by multiple requests it didn't make sense for each of the messages to have access to it.

The response to `CurrentBlockHeaderRequest{}` is the peer's local
current header. This can be used to get a rough idea of what the latest
block is as viewed by other peers on the network. The header can be
compared with a subset of peers to determine an efficient way of pulling
blocks from the network while syncing.

Initially, we modified the iteration message to include a `latest`
option, however, since the iteration message is shared by multiple
requests it didn't make sense for each of the messages to have access to
it.
@ittaysw
Copy link
Collaborator

ittaysw commented Dec 3, 2023

What is the use case of getting a rough idea?
Note there's the NewBlock message which propagates, so when getting it from a peer, you know that is the block it has.

@IronGauntlets
Copy link
Collaborator Author

IronGauntlets commented Jan 11, 2024

What is the use case of getting a rough idea?

When a new peer connects to the network, it has some idea of what height to request the blocks for, otherwise a peer could be requesting blocks which don't exist.

Note there's the NewBlock message which propagates, so when getting it from a peer, you know that is the block it has.

True, however, we don't want to wait for a new block to be propagated until a peer starts syncing. Also, I felt it would be good to request a peer's height.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants