Skip to content

docs: add mainnet credentials callout to RPC node guide #94

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
Zygimantass merged 2 commits into from
Feb 9, 2026
Merged

docs: add mainnet credentials callout to RPC node guide #94

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
047566a
docs: add mainnet credentials callout to RPC node guide
gakonst Feb 9, 2026
de3ae3c
fix: use vocs Callout component instead of directive syntax
gakonst Feb 9, 2026
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
6 changes: 6 additions & 0 deletions src/pages/guide/node/rpc.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,8 @@
description: Set up and run a Tempo RPC node for API access. Download snapshots, configure systemd services, and monitor node health and sync status.
---

import { Callout } from 'vocs'

# Running an RPC Node

RPC nodes provide API access to the Tempo network without participating in consensus.
Expand All @@ -19,6 +21,10 @@ tempo node \
--http.api eth,net,web3,txpool,trace
```

<Callout type="info">
For mainnet, you have to use the credentials in `--follow` that are issued to you by the Tempo team.
</Callout>

An RPC node running in follow mode is a **full node**. It fetches blocks from a trusted RPC endpoint, executes every transaction locally through the EVM, validates each block after execution, and stores complete block data with full state. The only trust assumption is block ordering: your node trusts the RPC endpoint to provide the correct sequence of blocks. All execution and validation happens locally on your machine.

By default, RPC nodes run in archive mode, meaning they do not prune historical state.
Expand Down