-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Bump testnet checkpoint and nMinimumChainWork/defaultAssumeValid params #2026
Conversation
blockhash: 0000000003aa53e24b6e60ef97642e4193611f2bcb75ea1fa8105f0b5ffd5242
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just bumping the checkpoint did not fix it, curious to see if the second part of the patch will work :)
utACK
@schinzelh have you tried reindexing after the bump? |
@UdjinM6 i think so, but i can try again just in case. The issue is that the nodes stay on the correct chain, but still throw
and keep on banning themselves from the network. |
@schinzelh I'm pretty sure reindexing should fix this but if not then that's going to be fixed by another patch I'm working on atm (hopefully) :) |
Alternatively, you can try to sync from scratch. |
@UdjinM6 you are right, reindexing with bumped checkpoint is fixing it. So utACK --> tested ACK :) |
Nice, thanks! :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK
New checkpoint should help new (or reindexed) nodes to stay on the right chain.
nMinimumChainWork
/defaultAssumeValid
should make sync a bit faster by skipping a lot of verifications in 2mb spam blocks.