Extend fork ID to timestamp-based forks #6324
Merged
Conversation
This file contains 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
|
some maybe-relate nil: #6321 |
This was referenced Dec 16, 2022
yperbasis
added a commit
to ledgerwatch/erigon-lib
that referenced
this pull request
Dec 16, 2022
Prerequisite for erigontech/erigon#6324
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Starting from Shanghai, forks are based on timestamps rather than block heights (see PR #6238). This PR extends EIP-2124 Fork ID to include timestamp-based blocks. See also ethereum/go-ethereum#25878.