Repository navigation
Conversation
This was referenced Sep 11, 2026
Contributor
Author
|
Closing because we decided to keep this behavior Base-local in base/base#5043 rather than add an upstream extension point. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Base is introducing 200ms blocks while retaining second-granular header timestamps, so valid consecutive blocks can share the same timestamp. The current
eth_simulateV1sanitizer rejects those explicit timestamps and rounds subsecond defaults up to one second.This adds opt-in timestamp generation and validation hooks to
Call, while preserving Reth's existing strictly-increasing behavior by default. Base uses the hooks in base/base#5023; the release-branch integration is base#19.