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: block.timestamp is not accurate #3398
base: main
Are you sure you want to change the base?
fix: block.timestamp is not accurate #3398
Changes from 1 commit
38e1f72
094e564
479ccfe
7b7bd2a
a38f57d
5af005b
06c1ca4
ad25d74
8e9752d
47f249e
386b536
16761cd
886abf3
d50917c
d161b67
1146c3c
4768ff1
225beda
ebcd2b4
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.
Sorry for not noticing this before, but
wait_for_next_tx()
usage is bogus, sinceupdates_manager.l2_block.timestamp
may refer to the timestamp of the previous block. This timestamp is used in theMempoolIO
implementation to checktimestamp_asserter_range
of the transaction. I think the easiest solution would be to create a tentative block timestamp before callingwait_for_next_tx()
if necessary. This circles back to the idea we've discussed about creating a block inUpdatesManager
early on, but not passing it to the VM until the first tx in the block (and adjusting the block timestamp with time before that). The adjustment likely has to be expressed as aStateKeeperIO
method since we don't want to rely on any sort of I/O (like getting the wall clock time) unconditionally. E.g., forExternalIO
, block timestamps must never be adjusted.To make invariants clearer, it may make sense to change
StateKeeperIO
to have 2 methods to create blocks:I think this would make the intended workflow obvious on the type system level.