-
Notifications
You must be signed in to change notification settings - Fork 11
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
[1.0.1] Handle block invariant checks during replay appropriately and in particular ensure --force-all-checks is respected #715
Conversation
…nts and verify_qc; rename several functions
Note:start |
|
||
// verify the QC proof against the claimed block | ||
bsp->verify_qc(qc_proof); | ||
return qc_proof; | ||
} |
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.
Be explicit with optional type otherwise you don't get return value optimization
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.
Thanks. Did not notice this before I pressed the green button. Will do a followup PR tomorrow.
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.
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
Currently QC block extension and finality header extension are not verified during replay.
This PR performs all the basic checks of Legacy, Transition, and Proper Savanna blocks during replay. If
--force-all-checks
is specified, a complete QC validation is performed.Resolves #693