Repository navigation
core/history: refactor pruning configuration - #34036
Merged
Merged
Conversation
| BlockHash: common.HexToHash("0x50c8cab760b2948349c590461b166773c45d8f4858cccf5a43025ab2960152e8"), | ||
| }, | ||
| params.SepoliaGenesisHash: { | ||
| BlockNumber: 7836331, |
Member
There was a problem hiding this comment.
WHere did you get this number? Just out of curiosity how to find the first block of a fork
Contributor
Author
There was a problem hiding this comment.
For mainnet you the info can be found on here https://ethereum.org/ethereum-forks/#pectra but for testnet I haven't found a single source. Once you find the block somewhere it can be double checked on etherscan because they show a banner for the fork blocks.
rjl493456442
approved these changes
Mar 18, 2026
noemiplatform
approved these changes
Apr 9, 2026
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
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.
This PR introduces a new type HistoryPolicy which captures user intent as opposed to pruning point stored in the blockchain which persists the actual tail of data in the database.
It is in preparation for the rolling history expiry feature.
It comes with a semantic change: if database was pruned and geth is running without a history mode flag (or explicit keep all flag) geth will emit a warning but continue running as opposed to stopping the world.