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

After connecting to network, user should send request for block headers #2

Open
tgoldenberg opened this issue Feb 12, 2018 · 0 comments

Comments

@tgoldenberg
Copy link
Owner

On initialization, the program should first look locally to see if block headers are stored.

If they are, they should be set and the last block header should be sent to the channel.

Once the last saved header is sent out, the program should await a response with block headers starting from the last one saved.

Once the program receives the block headers (a max of 50), it should set its "last block header" and reject incoming messages that are not set to it.

As the client accepts the block headers, it should validate their integrity. If any are not validated then the previous state of the chain should be accepted.

When the client receives a chunk of headers less than 50, it can send a verification request that the headers are up-to-date. The network can send a verification that this is true.

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

No branches or pull requests

1 participant