From 8038efe63db326192d32f0271fceae588edbfd15 Mon Sep 17 00:00:00 2001 From: Zygimantas <5236121+Zygimantass@users.noreply.github.com> Date: Thu, 19 Mar 2026 06:06:18 -0700 Subject: [PATCH 1/2] fix(rpc): remove pre-public artifact of running an rpc node --- src/pages/guide/node/rpc.mdx | 4 ---- 1 file changed, 4 deletions(-) diff --git a/src/pages/guide/node/rpc.mdx b/src/pages/guide/node/rpc.mdx index 23c628f2..741b4f73 100644 --- a/src/pages/guide/node/rpc.mdx +++ b/src/pages/guide/node/rpc.mdx @@ -21,10 +21,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. From 437cbd3678afc46c5dcd395db5b15d6624e00924 Mon Sep 17 00:00:00 2001 From: Zygimantas <5236121+Zygimantass@users.noreply.github.com> Date: Thu, 19 Mar 2026 06:06:46 -0700 Subject: [PATCH 2/2] fix(rpc): remove pre-public artifact of running an rpc node --- vocs.config.ts | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/vocs.config.ts b/vocs.config.ts index d6e574f2..94840ad5 100644 --- a/vocs.config.ts +++ b/vocs.config.ts @@ -15,8 +15,7 @@ export default defineConfig({ banner: { dismissable: false, backgroundColor: '#5B4CDB', - content: - 'Tempo Mainnet is live. [Read our announcement.](https://tempo.xyz/blog/mainnet) →', + content: 'Tempo Mainnet is live. [Read our announcement.](https://tempo.xyz/blog/mainnet) →', height: '40px', textColor: 'white', },