<!-- tempo-docs-context -->
> Source: [/docs/guide/node](https://tempo.xyz/developers/docs/guide/node.md)
> Section: [Tempo EVM](https://tempo.xyz/developers/docs/development.md). Build on Tempo EVM: wallets and keys, transactions and fees, TIP-20 Tokens, contracts, exchange, network details, nodes, protocol specifications, and changelog.
> [Documentation index](https://tempo.xyz/developers/llms.txt) · [Docs skill](https://tempo.xyz/developers/SKILL.md)

> Tempo MCP: Use `search`, `find_pages`, `read_page`, and `code` at `https://mcp.tempo.xyz` for Tempo and related documentation.
> If an indexed page is missing or reflects an older site, read this site’s [documentation index](https://tempo.xyz/developers/llms.txt) and Markdown pages directly.

<span id="run-a-tempo-node-validator-rpc-and-standby" />

# Run a node

Run Tempo infrastructure when you need your own RPC access or participate in validator operations. Most applications can start with the [public RPC endpoints](https://tempo.xyz/developers/docs/quickstart/connection-details).

## Choose a node type

| Node | Use it for | Start here |
| --- | --- | --- |
| RPC node | Read network state and serve JSON-RPC without participating in consensus. | [RPC setup](https://tempo.xyz/developers/docs/guide/node/rpc) |
| Validator | Participate in coordinated network operations. Onboarding requires coordination with the Tempo team. | [Validator responsibilities](https://tempo.xyz/developers/docs/guide/node/validator) |
| Standby node | Maintain infrastructure for validator failover. | [Failover](https://tempo.xyz/developers/docs/guide/node/validator-failover) |

A following RPC node verifies consensus finalization certificates and executes transactions locally. Its upstream must serve certified consensus data. Read [consensus and network identity](https://tempo.xyz/developers/docs/guide/node/consensus-and-dkg) for the trust model and key-rotation behavior.

<span id="rpc-node-path" />

## Run an RPC node

Check the [system requirements](https://tempo.xyz/developers/docs/guide/node/system-requirements), then [install the Tempo binary](https://tempo.xyz/developers/docs/guide/node/installation). Download a mainnet snapshot and start the node:

```bash [CLI]
tempo download --chain mainnet --archive

tempo node \
  --follow \
  --http --http.port 8545 \
  --http.api eth,net,web3,txpool,trace
```

Once the node serves RPC, read its sync status. `eth_syncing` returns `false` when it is no longer syncing, or an object with progress fields while syncing.

:::code-group
```bash [API (RPC)]
curl http://localhost:8545 -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_syncing","params":[]}'
```

```bash [CLI]
cast rpc eth_syncing --rpc-url http://localhost:8545
```
:::

The [RPC setup guide](https://tempo.xyz/developers/docs/guide/node/rpc) covers persistent services and health checks. Review [node security](https://tempo.xyz/developers/docs/guide/node/security) before exposing endpoints.

<span id="validator-operations" />

<span id="releases" />

## Monitor and upgrade

Use [monitoring](https://tempo.xyz/developers/docs/guide/node/validator-monitoring) to track node health and [troubleshooting](https://tempo.xyz/developers/docs/guide/node/validator-troubleshooting) to diagnose failures. For validators, follow [onboarding](https://tempo.xyz/developers/docs/guide/node/validator-setup), [topology](https://tempo.xyz/developers/docs/guide/node/validator-topology), and [key management](https://tempo.xyz/developers/docs/guide/node/validator-keys).

Track [network upgrades](https://tempo.xyz/developers/docs/guide/node/network-upgrades) for required operator actions and the [upgrade cadence](https://tempo.xyz/developers/docs/guide/node/upgrade-cadence) for rollout guidance. The [changelog](https://tempo.xyz/developers/docs/changelog) records software releases; [protocol upgrades](https://tempo.xyz/developers/docs/protocol/upgrades) describe changes to network rules.