From f2d94058e1774b784383109ff30081d7d24b2fae Mon Sep 17 00:00:00 2001 From: Yorick Downe Date: Tue, 29 Sep 2026 11:20:02 +0100 Subject: [PATCH] Mention stakewise-expiry --- website/docs/Usage/NodeTypes.mdx | 3 ++- website/docs/Usage/ResourceUsage.mdx | 2 +- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/website/docs/Usage/NodeTypes.mdx b/website/docs/Usage/NodeTypes.mdx index 87d40e0..0b48ba6 100644 --- a/website/docs/Usage/NodeTypes.mdx +++ b/website/docs/Usage/NodeTypes.mdx @@ -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` diff --git a/website/docs/Usage/ResourceUsage.mdx b/website/docs/Usage/ResourceUsage.mdx index e01ec67..d1aef92 100644 --- a/website/docs/Usage/ResourceUsage.mdx +++ b/website/docs/Usage/ResourceUsage.mdx @@ -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 |