-
Notifications
You must be signed in to change notification settings - Fork 677
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
Fix/5502 #5544
Conversation
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.
Nice
…o handle (now legacy) cases where the PoX anchor block does not arrive in order (or at all)
Wow so much red! Noice! |
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.
👍
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
This fixes #5502. I have confirmed it with a genesis sync. It works by preventing the chains coordinator from advancing the sortition view until the corresponding PoX anchor block is found. This is now an unconditional requirement, since we know for a fact that all reward cycles have a PoX anchor block (and as of Nakamoto, _msut- have one). It paves the way for removing the entirety of the affirmation map subsystem.