Skip to content

Update space #626

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

Merged
yorickdowne merged 1 commit into from
Oct 22, 2026
Merged

Update space #626

Show file tree
Hide file tree
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
3 changes: 2 additions & 1 deletion website/docs/Usage/NodeTypes.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,9 +20,10 @@ This is controlled by variables in `.env`, which can be set with `nano .env`. Sw
- `full`
- `rolling-expiry` - keeps ~5 months of history
- `pre-merge-expiry` - history since the merge, narrowly fits into 2TB but may soon need a 4TB drive
- `stakewise-expiry` - history as required by Stakewise. For all but Nethermind and Reth, this is a variant of rolling-expiry. If the operator DB is reset, an EL that uses Stakewise-specific rolling expiry will need to be resynced as well.
- `custom` - use whatever expiry and database configuration the client defaults to, and set additional parameters via `EL_EXTRAS` in `.env`

Please be careful with expiry options: Expired history also means expired receipts, which can throw protocols such as SSV and Stakewise for a loop. Both work with pre-merge-expiry, but will likely break with rolling expiry, unless they get receipts from another (unexpired) RPC endpoint.
Please be careful with expiry options: Expired history also means expired receipts, which can throw protocols such as SSV for a loop. SSV works with pre-merge-expiry, but will likely break with rolling expiry, unless they get receipts from another (unexpired) RPC endpoint.

`CL_NODE_TYPE` can be one of:
- `archive`
Expand Down
2 changes: 1 addition & 1 deletion website/docs/Usage/ResourceUsage.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ All clients continously prune state, and can expire history.
| Client | Version | Date | DB Full | DB Post-Merge | DB Rolling | RAM | Notes |
|--------|---------|------|---------|---------------|------------|-----|-------|
| Besu | v26.8.1 | September 2026 | >1.7 TiB | ~1.1 TiB | ~430 GiB | ~10 GiB | |
| Erigon | 3.6.0 | September 2026 | >1.7 TiB | ~1.1 TiB | ~590 GiB | ~18 GiB | Erigon will use available system RAM, but the OS will use it for other processes as needed |
| Erigon | 3.6.0 | September 2026 | ~1.6 TiB | ~1.1 TiB | ~590 GiB | ~18 GiB | Erigon will use available system RAM, but the OS will use it for other processes as needed |
| Ethrex | 26.0.0 | September 2026 | >1.7 TiB | ~1.6 TiB | n/a | ~17 GiB | ~30 GiB RAM while snap syncing. With history backfill. Full node is only back to Byzantium |
| Geth | 1.17.5 | September 2026 | >1.7 TiB | ~1.3 TiB | n/a | ~ 8 GiB | |
| Nethermind | 2.0.0 | September 2026 | ~1.6 TiB | ~1.2 TiB | ~450 GiB | ~10 GiB | Flat FlatDB, the default, ~13 GiB during sync |
Expand Down
Loading