From 915439c595e81b2bd3603e5f17859f4736b767fd Mon Sep 17 00:00:00 2001 From: Zygimantas <5236121+Zygimantass@users.noreply.github.com> Date: Wed, 11 Mar 2026 17:55:25 +0100 Subject: [PATCH] fix(node): prep for mainnet --- src/pages/guide/node/validator.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/pages/guide/node/validator.mdx b/src/pages/guide/node/validator.mdx index d592c07..4dd1602 100644 --- a/src/pages/guide/node/validator.mdx +++ b/src/pages/guide/node/validator.mdx @@ -38,12 +38,12 @@ The public key should match the output of the `generate-private-key` command. The process for running a validator node is very similar to [running a full node](/guide/node/rpc). -You should start by downloading the latest snapshot using `tempo download --chain `. Downloading the snapshot allows your validator to start participating in consensus much faster. +You should start by downloading the latest snapshot using `tempo download -u `. Downloading the snapshot allows your validator to start participating in consensus much faster. Once you've downloaded the snapshot and have been whitelisted on-chain, you can proceed to run the validator node as such: ```bash tempo node --datadir \ - --chain moderato \ + --chain \ --consensus.signing-key \ --consensus.fee-recipient \ --telemetry-url