-
Notifications
You must be signed in to change notification settings - Fork 288
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
chaincfg: Add checkpoints for upcoming release. #2370
Conversation
|
Matches
|
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.
Verified. Also checked those were in fact checkpoint candidates as returned by IsCheckpointCandidate()
.
@matheusd Thanks for also verifying via |
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.
matches
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.
LGTM - same output as everybody else
This adds checkpoints at the following heights: mainnet: - 237310 - 277940 - 318020 - 340120 - 362120 - 404170 - 424170 - 444170 - 464170 - 483600 testnet: - 148320 - 213120 - 347140 - 411940 - 476740 - 515730 Note that this also includes some historical checkpoints to limit the size of the gaps between each checkpoint to be around 3 months max. This is being done because recent optimizations have sped up processing to the point that larger gaps can trigger peers to get banned during IBD in some cases.
This adds checkpoints at the following heights:
mainnet
:testnet
:Note that this also includes some historical checkpoints to limit the size of the gaps between each checkpoint to be around 3 months max. This is being done because recent optimizations have sped up processing to the point that larger gaps can trigger peers to get banned during IBD in some cases.