Repository navigation
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
Collaborator
🟡 Heimdall Review Status
|
This branch was successfully deployed
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.
What changed? Why?
Updates the warning on Node Snapshots (
docs/specifications/node-operators/snapshots.mdx). The old text said "by mid-August" and "over the next few weeks", which are now out of date. The new text gives the exact cutoff: Base stopped publishing V1 node database snapshots on October 5, 2026. It also links the status notice and the V2 snapshot source. Operators who still use V1 storage are told to upgrade tobase-reth-nodev1.2.0 or later. The two migration paths stay, including the warning thatmigrate-v2is much slower and does not support non-archival nodes.Closes knowledge gap
gap-20260930-v1-node-snapshot-cutoff-date-exact: "Are Base V1 node snapshots still published, when is the exact cutoff/decommission date, and where do node operators find the V2 snapshot migration path?"Notes to reviewers
Primary sources:
base-reth-node download(recommended) vs.base-reth-node db migrate-v2(much slower, non-archival nodes not supported): https://github.com/base/base/releases/tag/v1.2.0Owner confirmation (Node/base-reth-node team) before merge: please confirm that the operational wording is right. Specifically, confirm that V1 snapshots are no longer served on either network, and that "v1.2.0 or later" is the right minimum version for V2 storage.
This replaces the
snapshots.mdxpart of #2092, which bundled several unrelated changes. The cross-link #2092 added todocs/upgrades/beryl/reth-v2.mdxis not included here.How has it been tested?
node scripts/lint-mdx.js --files-from=<changed files>: 0 errors, 0 warnings.node scripts/validate-docs-structure.js: the only failures are the existing/upgrades/denim/eip-8130redirect issues that are already on master. This PR does not touch them.Screenshots
N/A (text-only change)
Generated with Toshi