diff --git a/src/pages/cli/download.mdx b/src/pages/cli/download.mdx index ef0bc727..c60bc6b3 100644 --- a/src/pages/cli/download.mdx +++ b/src/pages/cli/download.mdx @@ -22,27 +22,20 @@ tempo download [flags] | `-u, --url ` | Download a specific snapshot URL | | `--list` | List available snapshots | | `--resumable` | Resume an interrupted download | -| `--minimal` | Download minimal snapshot (pruned state, suitable for validators) | -| `--archive` | Download full archive snapshot (suitable for RPC nodes) | +| `--archive` | Download an archive snapshot. Recommended for partner validators and RPC nodes. | ## Examples -Download the latest archive snapshot (for RPC nodes): +Download the latest recommended mainnet snapshot: ```bash -tempo download --archive +tempo download --chain mainnet --archive ``` -Download the latest minimal snapshot (for validators): +Download the latest recommended testnet snapshot: ```bash -tempo download --minimal -``` - -Download a snapshot for a specific chain: - -```bash -tempo download --archive --chain moderato +tempo download --chain moderato --archive ``` List available snapshots: diff --git a/src/pages/guide/node/installation.mdx b/src/pages/guide/node/installation.mdx index bbe84e93..318d42c5 100644 --- a/src/pages/guide/node/installation.mdx +++ b/src/pages/guide/node/installation.mdx @@ -49,19 +49,14 @@ docker logs tempo Downloading a snapshot lets your node skip syncing from genesis and start participating much faster. This is recommended for both RPC nodes and validators. ::::code-group -```bash [Minimal (validators)] -tempo download --chain mainnet --minimal -``` -```bash [Full (RPC / dApp backends)] -tempo download --chain mainnet -``` -```bash [Archive (indexers / RPC providers)] +```bash [Mainnet] tempo download --chain mainnet --archive ``` +```bash [Testnet] +tempo download --chain moderato --archive +``` :::: -For testnet, replace `mainnet` with `moderato`. See [snapshots.tempoxyz.dev](https://snapshots.tempoxyz.dev/) for detailed component sizes and download options. - ## Verifying Releases All release artifacts are cryptographically signed. We recommend verifying signatures before running any binary. diff --git a/src/pages/guide/node/validator-setup.mdx b/src/pages/guide/node/validator-setup.mdx index 7562ef41..ebf392d4 100644 --- a/src/pages/guide/node/validator-setup.mdx +++ b/src/pages/guide/node/validator-setup.mdx @@ -83,16 +83,16 @@ Once the Tempo team adds your validator on-chain, it will enter the active set i ## Running the validator -The process for running a validator node is very similar to [running a full node](/guide/node/rpc). +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. Downloading the snapshot allows your validator to start participating in consensus much faster. ::::code-group ```bash [Mainnet] -tempo download --chain mainnet +tempo download --chain mainnet --archive ``` ```bash [Testnet] -tempo download --chain moderato +tempo download --chain moderato --archive ``` ::::