Skip to content

docs: Avoid confusion around reth's full/archive node terminology #750

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
dknopik wants to merge 1 commit into
base: unstable
Choose a base branch
from
Open

docs: Avoid confusion around reth's full/archive node terminology #750

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
2 changes: 1 addition & 1 deletion docs/docs/pages/running_an_operator.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ flags are needed for your specific setup.
:::warning
The `reth` execution client currently prunes receipts of smart contracts by default. This prevents
Anchor (or any SSV node) from syncing. In order to run a `reth` node with Anchor, `reth` should be
run as a full node and [pruning](https://reth.rs/run/faq/pruning/) should be prevented.
prevented from [pruning](https://reth.rs/run/faq/pruning/) receipts, e.g. by running it as archive node.
:::


Expand Down
Loading