Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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(state-transition): skip execution payload timestamp validation on Bartio #2147
fix(state-transition): skip execution payload timestamp validation on Bartio #2147
Changes from 9 commits
1e120b3
5d2cd2c
675abd4
d32eae0
73b7780
94e55ee
d7fad67
25c5633
6a21637
7480048
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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 consolidated variables here
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.
Should this be just
>
? Why are we failing on the==
case?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 is done to guarantee strict monotonicity of payload timestamp and it works for the following reason.
NextPayloadTimestamp is set to
consensus_block.Time + 1 sec
, while payload time is equal to:parent_consensus_block.Time + 1 sec
if payload is built optimistically (i.e. built whileparent_consensus_block
was being verified)consensus_block.Time
is payload is built non-optimistically (i.e. built just in time whenPrepareBlock
request arrived forconsensus_block
.Note that
consensus_block.Time-parent_consensus_block.Time > 1 sec
.So in both cases the bound is strict because
LMK if this is clear and if you see any error. I really should draw some documentation around this, as soon as I have a second
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.
What we should do that don't do currently is validate consensus configs and making sure that no block can be finalized before 1 second.
This is in line with current specs and it is reasonable I think, but not enforce in code.