From 102a07b60c52e207d111c218559533808d3d6889 Mon Sep 17 00:00:00 2001 From: Derek Cofausper <256792747+decofe@users.noreply.github.com> Date: Thu, 19 Mar 2026 00:13:38 +0000 Subject: [PATCH] docs: remove mainnet credentials callout from RPC guide Co-authored-by: Alexey Shekhirin <5773434+shekhirin@users.noreply.github.com> Amp-Thread-ID: https://ampcode.com/threads/T-019d0370-5552-7049-afd1-c5d1a72f4c7f --- src/pages/guide/node/rpc.mdx | 6 ------ 1 file changed, 6 deletions(-) diff --git a/src/pages/guide/node/rpc.mdx b/src/pages/guide/node/rpc.mdx index 23c628f2..814d6ec6 100644 --- a/src/pages/guide/node/rpc.mdx +++ b/src/pages/guide/node/rpc.mdx @@ -2,8 +2,6 @@ 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. @@ -21,10 +19,6 @@ tempo node \ --http.api eth,net,web3,txpool,trace ``` - -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.