From 047566a8219a8b8dc293980a9c69898272478822 Mon Sep 17 00:00:00 2001 From: Georgios Konstantopoulos Date: Mon, 9 Feb 2026 19:48:36 +0000 Subject: [PATCH 1/2] docs: add mainnet credentials callout to RPC node guide Amp-Thread-ID: https://ampcode.com/threads/T-019c43f2-1db9-71fa-a274-8e038c0559fa Co-authored-by: Amp --- src/pages/guide/node/rpc.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/pages/guide/node/rpc.mdx b/src/pages/guide/node/rpc.mdx index 106bedb6..cac43a48 100644 --- a/src/pages/guide/node/rpc.mdx +++ b/src/pages/guide/node/rpc.mdx @@ -19,6 +19,10 @@ tempo node \ --http.api eth,net,web3,txpool,trace ``` +:::info +For mainnet, you have to use the credentials in `--follow` that are issued to you by the Tempo team. +::: + 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. From de3ae3c9983646ad46fa5c1ec3ecf9f3f149d1fe Mon Sep 17 00:00:00 2001 From: Georgios Konstantopoulos Date: Mon, 9 Feb 2026 19:51:37 +0000 Subject: [PATCH 2/2] fix: use vocs Callout component instead of directive syntax Amp-Thread-ID: https://ampcode.com/threads/T-019c43f2-1db9-71fa-a274-8e038c0559fa Co-authored-by: Amp --- src/pages/guide/node/rpc.mdx | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/src/pages/guide/node/rpc.mdx b/src/pages/guide/node/rpc.mdx index cac43a48..1b1bd098 100644 --- a/src/pages/guide/node/rpc.mdx +++ b/src/pages/guide/node/rpc.mdx @@ -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. @@ -19,9 +21,9 @@ tempo node \ --http.api eth,net,web3,txpool,trace ``` -:::info + For mainnet, you have to use the credentials in `--follow` that are issued to you by the Tempo team. -::: + 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.