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

[Performance] Move synchronization to headers-first sync. #972

Open
furszy opened this issue Aug 1, 2019 · 1 comment
Open

[Performance] Move synchronization to headers-first sync. #972

furszy opened this issue Aug 1, 2019 · 1 comment

Comments

@furszy
Copy link

furszy commented Aug 1, 2019

As the title says, would be great to move the synchronization process to headers-first sync.
It will definitely decrease the network latency in a big manner, the amount of data that needs to be downloaded and therefore the wallet initial sync.

This has been partially developed in the past inside our code, it requires further efforts to finish the functionality.

The only problem here and what needs to be described really well in a proper document is the PoS blocks validation and DoS spam protection.

We already added a sync spam filter when the "fake stake" attack was proposed. The topic, once headers-first is mostly done, will mostly be if this protection is enough or if there is a need for something different for PoS.

@barrystyle
Copy link

Not done to open old wounds, but more as an interesting aside (also with minimal validation) however it seems the protocol can be made to work...

ProjectMerge/merge-legacy@26aac8a

Perhaps some qtum-type method could be applied in future, where some of the required validation data could be placed in the blockheader?

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

No branches or pull requests

2 participants