fix: add missing hardfork timestamps to mainnet and hoodi genesis#53
Open
fix: add missing hardfork timestamps to mainnet and hoodi genesis#53
Conversation
The genesis.json files were missing the timestamp-based hardfork activation fields. When geth starts with --morph/--morph-hoodi flags, it overrides the stored config with the hardcoded MorphMainnetChainConfig / MorphHoodiChainConfig, so sync still works for geth. However, other clients (e.g. morph-reth) that rely purely on genesis.json to determine hardfork activation would silently skip these hardforks. Mainnet (chain ID 2818) - from go-ethereum MorphMainnetChainConfig: morph203Time: 1747029600 (2025-05-12) viridianTime: 1762149600 (2025-10-04) emeraldTime: 1767765600 (2026-01-07) Hoodi (chain ID 2910) - from go-ethereum MorphHoodiChainConfig: viridianTime: 1761544800 (2025-10-27) emeraldTime: 1766988000 (2025-12-29) (morph203Time: 0 was already present) Verified: geth init succeeds with unchanged genesis hashes.
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.
Summary
morph203Time,viridianTime,emeraldTimetomainnet/geth-data/genesis.jsonviridianTime,emeraldTimetohoodi/geth-data/genesis.jsonBackground
go-ethereum determines hardfork activation from hardcoded configs (
MorphMainnetChainConfig/MorphHoodiChainConfiginparams/config.go). When geth starts with--morphor--morph-hoodi, it always overwrites the stored chain config with these hardcoded values — so geth sync works regardless of what's in genesis.json.However, other clients (e.g. morph-reth) rely purely on genesis.json to determine hardfork activation. Without these fields, timestamp-based hardforks (Morph203, Viridian, Emerald) are never activated.
Values (from go-ethereum
params/config.go)Mainnet (chain ID 2818):
morph203TimeviridianTimeemeraldTimeHoodi (chain ID 2910):
viridianTimeemeraldTime(
morph203Time: 0was already present in hoodi)Test Plan
geth init mainnet/geth-data/genesis.json— exit 0, genesis hash unchanged (649c9b..cfa7a9)geth init hoodi/geth-data/genesis.json— exit 0, genesis hash unchanged (2cbcff..bfc35c)