docs: add Geth-to-Reth migration guide for Base V1 upgrade#1033
Open
docs: add Geth-to-Reth migration guide for Base V1 upgrade#1033
Conversation
Several node operators are blocked on the Geth-to-Reth migration ahead of the Base V1 activation in early May 2026 (see base#1030). There is currently no migration guide in the repository — operators are piecing together steps from Discord, the README, and the snapshot docs. Added MIGRATING.md covering the full migration path: - Stop node and pull latest base/node - Set CLIENT=reth and USE_BASE_CONSENSUS=true - Bootstrap from official snapshot (avoids multi-day sync from genesis) - Start node and verify migration with RPC health checks - Troubleshooting section for the four most common failure modes - Rollback instructions (pre-activation only) - Environment variable reference table Closes base#1030 (partially — this does not extend the deadline but gives operators a clear path to complete the migration in time).
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.
Problem
Several node operators are blocked on the Geth-to-Reth migration ahead of Base V1 activation in early May 2026 (see #1030). There is currently no migration guide in the repository — operators are piecing together steps from Discord, the README, and the snapshot docs separately.
Solution
Add
MIGRATING.mdwith a complete, step-by-step migration guide covering:base/nodeCLIENT=rethandUSE_BASE_CONSENSUS=trueweb3_clientVersion,eth_blockNumber,net_peerCount)Why this matters
The V1 deadline is days away. Operators who started Reth from genesis are still syncing (#1030). The snapshot bootstrap path cuts this from days to hours — but it wasn't documented in one place. This guide gives operators a clear, actionable path to complete the migration in time.
Closes #1030 (partially — the guide gives operators the fastest path to complete migration; extending the deadline is a separate decision for the team).