<!-- tempo-docs-context -->
> Source: [/docs/guide/node/security](https://tempo.com/developers/docs/guide/node/security.md)
> Section: [Tempo EVM](https://tempo.com/developers/docs/development.md). Build on Tempo EVM: wallets and keys, payments, transactions and fees, TIP-20 Tokens, contracts, exchange, network details, nodes, protocol specifications, and changelog.
> [Documentation index](https://tempo.com/developers/llms.txt) · [Docs skill](https://tempo.com/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.com/developers/llms.txt) and Markdown pages directly.

# Node security: best practices for operators

Protect your validator from impersonation, unauthorized access, and operational mistakes.

## Key management

Your signing key is the ed25519 key that identifies your validator in consensus, the protocol validators use to propose and vote on blocks. It's the most sensitive asset on your validator. Anyone with access to it can impersonate your node in consensus.

* **Restrict file permissions** — set `chmod 600` on key files so only the node process user can read them.
* **Never share your private key** — the Tempo team will never ask for it.
* **Use different keys for testnet and mainnet** — do not reuse signing keys or the keys that control your validator operator address across networks; a testnet compromise should never put your mainnet validator at risk.
* **Rotate keys periodically** — use [key rotation](https://tempo.com/developers/docs/guide/node/validator-lifecycle#rotate-validator-identity) to swap to a new ed25519 key without leaving the committee, the set of validators that run consensus in an epoch.
* **Separate the operator address** — the validator operator address is the Ethereum address that authorizes your validator's onchain configuration changes, such as IP updates, rotation, and ownership transfer. Use a dedicated address, not a general-purpose hot wallet.

[Managing validator keys](https://tempo.com/developers/docs/guide/node/validator-keys) lists every validator key and address, including the fee recipient and signing share, and shows how to generate the signing key.

## Network configuration

:::info
Deploy validators using the [validator network topology](https://tempo.com/developers/docs/guide/node/validator-topology). Isolate the validator, allow direct consensus traffic only with other validators, and route execution P2P through internal follower RPC nodes. A follower RPC node is a non-validating Tempo node you run to sync blocks and accept transactions for the validator.
:::

Tempo's networking protections complement the firewall and isolation rules in the validator topology. The node:

* Only accepts consensus connections from validators that can prove their identity
* Restricts consensus connections to trusted validator IP addresses registered onchain
* Rate-limits connections and messages in both consensus and execution layers

### Recommendations

* **Expose only the required ports** — see [Ports](https://tempo.com/developers/docs/guide/node/system-requirements#ports) for which ports need public access vs. internal-only.
* **Keep ingress addresses unique** — your ingress address is the inbound `IP:port` registered onchain for consensus peers. The validator registry enforces uniqueness, but verify your registered `IP:port` is correct after infrastructure changes.
* **Use a dedicated machine** — avoid running other internet-facing services on the same host as your validator.

## Release verification

Always verify release artifacts before running them. Tempo signs all binaries and Docker images — see [Verifying Releases](https://tempo.com/developers/docs/guide/node/installation#verifying-releases) for GPG, build provenance, and SHA256 verification instructions.

## Time synchronization

An unsynchronized clock can cause your node to reject valid blocks or produce blocks that other validators reject. Use `chrony` or `ntpd`. `systemd-timesyncd`, the default on many minimal VMs, isn't precise enough. See [Time Synchronization](https://tempo.com/developers/docs/guide/node/system-requirements#time-synchronization) for setup instructions.

## Data integrity

* **Never delete the data directory and re-sync with the same signing key** — the node loses its record of past votes, so it risks double-signing: casting conflicting votes. Recovering requires [rotating to a new identity](https://tempo.com/developers/docs/guide/node/validator-lifecycle#resetting-your-validators-data). Deleting the `<datadir>/consensus` subdirectory also removes consensus certificates the node needs at startup. Coordinate recovery from a snapshot with the Tempo team. [Signing-share recovery](https://tempo.com/developers/docs/guide/node/validator-keys#signing-share-recovery), which restores the node's share of the committee's signing key, doesn't replace those certificates.
* **Back up your signing key** — if the key file is lost and no backup exists, you will need to rotate to a new key and coordinate with the Tempo team.

## Staying up to date

* Subscribe to [Tempo GitHub releases](https://github.com/tempoxyz/tempo/releases) for security patches and upgrade announcements.
* Review the [Upgrade Cadence](https://tempo.com/developers/docs/guide/node/upgrade-cadence) for how far ahead Tempo announces testnet and mainnet upgrades.
* Apply Required upgrades before the activation block, the block where the new protocol rules take effect. Required upgrades are consensus-breaking, so a node that misses one forks off the network.
