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

Warp syncing shouldn't be a one time process #1109

Closed
tomaka opened this issue Sep 5, 2023 · 0 comments · Fixed by #1591
Closed

Warp syncing shouldn't be a one time process #1109

tomaka opened this issue Sep 5, 2023 · 0 comments · Fixed by #1591

Comments

@tomaka
Copy link
Contributor

tomaka commented Sep 5, 2023

Imagine this situation: the light client starts, connects to a node, and warp syncs to block 500. It then switches to "all forks syncing".
Later, it connects to a node that advertises block 100000.

In that situation, the light client should try to warp sync to block 100000 from that other node while keeping in mind that this other node could be malicious.

Basically, the AllSync state machine should continue running the warp sync state machine even after it's done.

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 a pull request may close this issue.

1 participant