Skip to content

add full node details to snapshot FAQ #1488

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
roethke wants to merge 1 commit into
base: master
Choose a base branch
from
Open

add full node details to snapshot FAQ #1488

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions docs/base-chain/node-operators/snapshots.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,3 +85,15 @@ If you are running the [historical proofs ExEx](/base-chain/node-operators/run-a
| Mainnet | `aria2c -c -x 16 -s 16 "https://mainnet-reth-proofs-snapshots.base.org/$(curl -s https://mainnet-reth-proofs-snapshots.base.org/latest)"` |

The restore process is the same as above — follow the [Restoring from Snapshot](#restoring-from-snapshot) steps using this archive instead.

## FAQ

<AccordionGroup>
<Accordion title="Why does Base provide a Pruned snapshot instead of a Full node snapshot?">

In Reth, a "full" node is just a pruned node with a specific preset rather than a distinct node type. Reth's `--full` preset retains the last **10,064 blocks** (~1.4 days on Ethereum; ~5-6 hours on Base due to faster block times).

Base's _pruned_ snapshot uses a 31-day rolling retention window instead. If a smaller storage footprint is preferred, you can override `reth.toml` to match the 10,064-block preset.

</Accordion>
</AccordionGroup>
Loading