From 7cb3681bb515e9518dddeffe5237ccf370992b74 Mon Sep 17 00:00:00 2001 From: Hamdi Allam Date: Tue, 19 May 2026 10:19:20 -0400 Subject: [PATCH 1/7] not about certified follow mode --- src/pages/guide/node/rpc.mdx | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/src/pages/guide/node/rpc.mdx b/src/pages/guide/node/rpc.mdx index 95c6e1c1..1477724a 100644 --- a/src/pages/guide/node/rpc.mdx +++ b/src/pages/guide/node/rpc.mdx @@ -25,6 +25,20 @@ An RPC node running in follow mode is a **full node**. It fetches blocks from a By default, RPC nodes run in archive mode, meaning they do not prune historical state. +## Certified Follow mode + +Soon to be the default, the follower can be configured to run without trusting the RPC endpoint. In order for this to work, the endpoint must serve consensus rpcs that the follower can use to validate peered execution state. The public endpoint for the Moderato testnet supports these rpcs + +``` +tempo node \ + --follow \ + --follow.experimental.certify + --http --http.port 8545 \ + --http.api eth,net,web3,txpool,trace +``` + +If following against a custom endpoint, it must serve the consensus rpcs (default true for validator nodes). RPC nodes running with `--follow.experimental.certify` will serve these rpcs. + ## Example Systemd Service ```bash /dev/null/systemd.sh#L1-55 From 1eb2642c6c9f0451aea64ea7baa3a2472434c07a Mon Sep 17 00:00:00 2001 From: Hamdi Allam Date: Tue, 19 May 2026 10:36:45 -0400 Subject: [PATCH 2/7] nits --- src/pages/guide/node/rpc.mdx | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/src/pages/guide/node/rpc.mdx b/src/pages/guide/node/rpc.mdx index 1477724a..fe1cde82 100644 --- a/src/pages/guide/node/rpc.mdx +++ b/src/pages/guide/node/rpc.mdx @@ -25,19 +25,21 @@ An RPC node running in follow mode is a **full node**. It fetches blocks from a By default, RPC nodes run in archive mode, meaning they do not prune historical state. -## Certified Follow mode +## Certified Follow Mode -Soon to be the default, the follower can be configured to run without trusting the RPC endpoint. In order for this to work, the endpoint must serve consensus rpcs that the follower can use to validate peered execution state. The public endpoint for the Moderato testnet supports these rpcs +Soon to be the default, the follower can be configured to run without trusting the RPC endpoint. In order for this to work, the endpoint must serve consensus rpcs that the follower can use to validate peered execution state. -``` +**NOTE**: Only the Moderato testnet supports running a follower in this mode + +```bash tempo node \ --follow \ - --follow.experimental.certify + --follow.experimental.certify \ --http --http.port 8545 \ --http.api eth,net,web3,txpool,trace ``` -If following against a custom endpoint, it must serve the consensus rpcs (default true for validator nodes). RPC nodes running with `--follow.experimental.certify` will serve these rpcs. +If following against a custom endpoint, it must serve the consensus rpcs (default true for validator nodes). RPC nodes can only follow certified from other RPC nodes running in the same configuration. ## Example Systemd Service From 65d5647e10a00628c4cea2f8f7e4aed0564ebadd Mon Sep 17 00:00:00 2001 From: Derek <256792747+decofe@users.noreply.github.com> Date: Wed, 20 May 2026 10:47:45 +0000 Subject: [PATCH 3/7] Update RPC node quick start callout --- src/pages/guide/node/rpc.mdx | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/src/pages/guide/node/rpc.mdx b/src/pages/guide/node/rpc.mdx index fe1cde82..3c3b5c76 100644 --- a/src/pages/guide/node/rpc.mdx +++ b/src/pages/guide/node/rpc.mdx @@ -10,6 +10,10 @@ RPC nodes provide API access to the Tempo network without participating in conse ## Quick Start + +Trusted (uncertified) RPC nodes will be deprecated. To run without trusting the RPC endpoint, use [Trustless RPC Nodes](#trustless-rpc-nodes). + + ```bash /dev/null/quickstart.sh#L1-15 # Download snapshot (this will help you sync much faster) tempo download --archive @@ -25,7 +29,7 @@ An RPC node running in follow mode is a **full node**. It fetches blocks from a By default, RPC nodes run in archive mode, meaning they do not prune historical state. -## Certified Follow Mode +### Trustless RPC Nodes Soon to be the default, the follower can be configured to run without trusting the RPC endpoint. In order for this to work, the endpoint must serve consensus rpcs that the follower can use to validate peered execution state. From 92a37193a8e3d385c112fa13a4edf631be05962f Mon Sep 17 00:00:00 2001 From: Derek <256792747+decofe@users.noreply.github.com> Date: Wed, 20 May 2026 10:56:05 +0000 Subject: [PATCH 4/7] Add trustless RPC node availability callouts --- src/pages/guide/node/rpc.mdx | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/src/pages/guide/node/rpc.mdx b/src/pages/guide/node/rpc.mdx index 3c3b5c76..19a0ced2 100644 --- a/src/pages/guide/node/rpc.mdx +++ b/src/pages/guide/node/rpc.mdx @@ -33,7 +33,13 @@ By default, RPC nodes run in archive mode, meaning they do not prune historical Soon to be the default, the follower can be configured to run without trusting the RPC endpoint. In order for this to work, the endpoint must serve consensus rpcs that the follower can use to validate peered execution state. -**NOTE**: Only the Moderato testnet supports running a follower in this mode + +Trustless RPC nodes are supported in release 1.7.1 and onward. + + + +2nd order RPC nodes, which follow other RPC nodes instead of validators, are currently only supported on the Moderato testnet. + ```bash tempo node \ From 82a6499993be0f9fc2bdc9c4dab59b8647e10032 Mon Sep 17 00:00:00 2001 From: Derek <256792747+decofe@users.noreply.github.com> Date: Wed, 20 May 2026 11:02:02 +0000 Subject: [PATCH 5/7] Clean up trustless RPC callout --- src/pages/guide/node/rpc.mdx | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/src/pages/guide/node/rpc.mdx b/src/pages/guide/node/rpc.mdx index 19a0ced2..bac90e28 100644 --- a/src/pages/guide/node/rpc.mdx +++ b/src/pages/guide/node/rpc.mdx @@ -31,14 +31,10 @@ By default, RPC nodes run in archive mode, meaning they do not prune historical ### Trustless RPC Nodes -Soon to be the default, the follower can be configured to run without trusting the RPC endpoint. In order for this to work, the endpoint must serve consensus rpcs that the follower can use to validate peered execution state. +The follower can be configured to run without trusting the RPC endpoint. In order for this to work, the endpoint must serve consensus rpcs that the follower can use to validate peered execution state. -Trustless RPC nodes are supported in release 1.7.1 and onward. - - - -2nd order RPC nodes, which follow other RPC nodes instead of validators, are currently only supported on the Moderato testnet. +Trustless RPC nodes are supported in release 1.7.1 and onward. 2nd order RPC nodes, which follow other RPC nodes instead of validators, are currently only supported on the Moderato testnet. ```bash From 8daf1811eca985dde6432ce47c72590ce61bc126 Mon Sep 17 00:00:00 2001 From: Derek <256792747+decofe@users.noreply.github.com> Date: Wed, 20 May 2026 11:09:32 +0000 Subject: [PATCH 6/7] Refine trustless RPC node wording --- src/pages/guide/node/rpc.mdx | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/src/pages/guide/node/rpc.mdx b/src/pages/guide/node/rpc.mdx index bac90e28..d1341cde 100644 --- a/src/pages/guide/node/rpc.mdx +++ b/src/pages/guide/node/rpc.mdx @@ -31,7 +31,7 @@ By default, RPC nodes run in archive mode, meaning they do not prune historical ### Trustless RPC Nodes -The follower can be configured to run without trusting the RPC endpoint. In order for this to work, the endpoint must serve consensus rpcs that the follower can use to validate peered execution state. +RPC nodes can verify certificates before executing blocks. Trustless RPC nodes are supported in release 1.7.1 and onward. 2nd order RPC nodes, which follow other RPC nodes instead of validators, are currently only supported on the Moderato testnet. @@ -45,8 +45,6 @@ tempo node \ --http.api eth,net,web3,txpool,trace ``` -If following against a custom endpoint, it must serve the consensus rpcs (default true for validator nodes). RPC nodes can only follow certified from other RPC nodes running in the same configuration. - ## Example Systemd Service ```bash /dev/null/systemd.sh#L1-55 From 5a527035bd5d7673a7b63cafd39269bb676d609d Mon Sep 17 00:00:00 2001 From: Derek <256792747+decofe@users.noreply.github.com> Date: Wed, 20 May 2026 11:16:59 +0000 Subject: [PATCH 7/7] Reorder trustless RPC callout --- src/pages/guide/node/rpc.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/pages/guide/node/rpc.mdx b/src/pages/guide/node/rpc.mdx index d1341cde..e2d68d69 100644 --- a/src/pages/guide/node/rpc.mdx +++ b/src/pages/guide/node/rpc.mdx @@ -31,12 +31,12 @@ By default, RPC nodes run in archive mode, meaning they do not prune historical ### Trustless RPC Nodes -RPC nodes can verify certificates before executing blocks. - Trustless RPC nodes are supported in release 1.7.1 and onward. 2nd order RPC nodes, which follow other RPC nodes instead of validators, are currently only supported on the Moderato testnet. +RPC nodes can verify certificates before executing blocks by suppling the `--follow.experimental.certify` flag: + ```bash tempo node \ --follow \