op/zora/mainnet: add missing hardfork timestamps to genesis.json #21
Reference in New Issue
Block a user
Delete Branch "issue-189"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
zora-mainnet-op-reth-pruned-traceon rpc-de-33 is stuck at block 0 / DRPC EU-West shows 100% unavailable.Root cause (confirmed by cursor on rpc-de-33):
op/zora/mainnet/genesis.jsonconfig block only containsregolithTime: 0(Bedrock/Regolith only). Op-reth starts at block 0 and op-node feeds current-head payloads (~block 47,708,000) which include withdrawals (Canyon activates Shanghai). Op-reth rejects every payload with "withdrawals pre-Shanghai" → 10,000+ failures → node stays stuck at block 0 forever.Fix
Added the following hardfork timestamps to the
configsection ofop/zora/mainnet/genesis.json:Also added/updated the
optimismconfig section:Values sourced from the superchain-registry zora.toml and the rollup.json already present on rpc-de-33 (which has the correct fork schedule).
Verification
./update.sh(filteredop.zora.mainnetand full run) completed with 0 errors/configmount for./op/zora/mainnet:/configserving the updated genesis.jsonafafaea4299d9c95a80e91665e47d6832fe5468cDeploy notes
After merge: deploy to rpc-de-33 via
deploy-compose-repo. The datadir volume (rpc_zora-mainnet-op-reth-pruned-trace) is only 2.7 MB (never synced), so wiping on force-recreate is safe. Node will start fresh from genesis with correct fork schedule and begin syncing normally.(vibe-node issue #189)