Document official storage v2 snapshots and bera-reth download - #93
Draft
camembera wants to merge 9 commits into
Draft
Document official storage v2 snapshots and bera-reth download#93camembera wants to merge 9 commits into
camembera wants to merge 9 commits into
Conversation
Point operators at fetch-berachain-snapshot-v2 for Bepolia, keep the v1 script for mainnet and community packs, and record that Reth honors the on-disk layout after a restore.
Storage v2 rides both Mainnet and Bepolia; guides' fetch-berachain-snapshot script drops the -v2 suffix. Adds a migrating-from-v1 walkthrough and a plain-prose bera-reth download reference with a link to reth's own pruning docs for --full.
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
camembera
commented
Aug 27, 2026
camembera
left a comment
Collaborator
Author
There was a problem hiding this comment.
Reviewed against Manny's Slack notes and what is live today.
Three content edits on snapshots.mdx:
- Cut the hot/cold-layer plus checksum-retry paragraphs (checksum retry already lives under
bera-reth download). - Put the sticky-datadir / restore-is-the-migration paragraph in a Warning, not another restatement in the migrating section.
- Put concrete Mainnet and Bepolia
manifest.jsonURLs on the--manifest-urlbullet. Keep the flag for third-party snapshots; once bera-reth #281 lands, drop it from Required for official--chain mainnet|bepolia.
Merge gates the PR already names are still open: snapshots.berachain.com and bepolia.snapshots.berachain.com still list tar.lz4 bundles, and guides still ships both fetch-berachain-snapshot.js and fetch-berachain-snapshot-v2.js. Do not merge until those match this page.
Keep the snapshots nav entry; drop the removed geth-to-reth page.
The paths were constructed, not verified. Operators copy the URL from the snapshot site instead, and the examples use a placeholder.
Explain why an operator would move to storage v2 without the layout internals: upstream Reth's measured disk savings per node preset, faster persistence, and the announced removal of storage v1 support. Reth 2.0 committed to dropping storage v1 but stated the deprecation date would be communicated separately, so avoid claiming a date exists. Note the in-place bera-reth db migrate-v2 converter rather than asserting a snapshot restore is the only path. Also run prettier over both pages, which earlier commits missed.
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.
Summary
nodes/operations/snapshots.mdx: storage v1 vs v2, what Bera-Reth does with storage v2, migrating from v1 to v2, a plain-prosebera-reth downloadreference (with a link to reth's pruning docs for--full), and the official restore walkthrough viafetch-berachain-snapshot.js.-v2suffix — both land via separate in-flight work (BERA-934, guides #435).Test plan
mint validatenpx prettier --check(via--write, clean)