-
Notifications
You must be signed in to change notification settings - Fork 673
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
hotfix: remove chain stall race condition #5508
base: master
Are you sure you want to change the base?
Conversation
… consensus_hash field, not the canonical tip
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.
Overall this LGTM! Great find and the fix in the validation endpoint makes a lot of sense.
Ah, yes, you're right -- |
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.
🙌
Todo: the proposal validation logic needs to load the current burn view -- it's either the burn view in the block's |
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!
This fixes a race condition in the block proposal API endpoint whereby the node was incorrectly loading the sortition view from its view of the canonical sortition tip, instead of the sortition tip identified by the block's header's
consensus_hash
field. Doing this lead to a chain-halt due to a race condition.Here's what I'm pretty sure happened, but could use some extra validation:
burn-block-height