<!-- tempo-docs-context -->
> Source: [/docs/guide/node/validator-lifecycle](https://tempo.com/developers/docs/guide/node/validator-lifecycle.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.

# Controlling validator lifecycle

Stop, reset, reconfigure, and deactivate a Tempo validator.

A validator is a node that proposes and votes on blocks. Validators that run consensus in an epoch, a period of about 3 hours, form the committee. Each epoch, a [DKG ceremony](https://tempo.com/developers/docs/guide/node/consensus-and-dkg) reshares the committee's signing key: dealers distribute key shares and players receive them.

## Starting and stopping

Use `SIGINT` (Ctrl+C) or `SIGTERM` to gracefully stop the node:

```bash
# If running directly
kill -INT <pid>

# If running via systemd
sudo systemctl stop tempo
```

The node will finish processing the current block before shutting down. Avoid using `SIGKILL` as it may corrupt the database.

## Resetting your validator's data

:::danger
**You cannot reset a validator's data and continue with the same identity.** Doing so risks inconsistent voting, which can cause irrecoverable network safety failures.
:::

To reset your validator's data, rotate to a new validator identity: a new ed25519 consensus signing key registered under your validator entry. This requires coordinating with the Tempo team to deactivate your old identity and register a new one. For the Tempo team, this is a routine operation, so reach out.

:::info
Self-service data resets are coming soon. Once available, you will be able to rotate to a new identity and reset your data without coordinating with the Tempo team. See [Rotate validator identity](https://tempo.com/developers/docs/guide/node/validator-lifecycle#rotate-validator-identity).
:::

## Managing your validator

The `tempo consensus` commands on this page submit transactions to the [ValidatorConfig V2 precompile](https://tempo.com/developers/docs/protocol/tips/tip-1017), Tempo's onchain validator registry. They sign from the validator operator address, the Ethereum address that controls your validator entry. That address doesn't need a plaintext private key. Add the [signer flag](https://tempo.com/developers/docs/guide/node/validator-keys#validator-operator-address-custody) that matches your custody, such as `--ledger`, `--aws`, or `--wallet-key <PATH>`. [Fee-token selection](https://tempo.com/developers/docs/guide/node/validator-lifecycle#choose-the-validator-fee-token) is the exception: it signs from the fee-recipient address.

Commands take the validator as `<address/pubkey/index>`: its operator address, its ed25519 consensus public key, or its index. The index is a number that stays the same when you rotate the signing key. [Validator lookup](https://tempo.com/developers/docs/guide/node/validator-status#look-up-your-validator) shows all three.

:::info[Preview or confirm transactions]
For `tempo consensus` commands, use `--dry-run` to print the target contract address and calldata without signing or sending; it does not simulate execution. Use `--yes` to skip the confirmation prompt when sending.
:::

### Rotate validator identity

Follow [validator rotation](https://tempo.com/developers/docs/guide/node/validator-rotation#rotate-validator-identity) to change the signing public key while preserving your validator index. You run a replacement node with the new signing key, a separate data directory, and a different ingress address, then register it. Keep the old validator running until [validator lookup](https://tempo.com/developers/docs/guide/node/validator-status#look-up-your-validator) shows `in_committee: false`. Until then, it still has committee duties.

### Update IP addresses

Follow [update IP addresses](https://tempo.com/developers/docs/guide/node/validator-rotation#update-ip-addresses) to change your registered ingress address (the inbound `IP:port` peers connect to) or egress address (the outbound IP) while keeping the same public key.

### Update the fee recipient

The fee recipient is the address that receives fees from blocks your validator proposes. It's stored onchain in your validator entry. A change takes effect from the next finalized block.

:::code-group
```bash [Mainnet]
tempo consensus set-validator-fee-recipient <address/pubkey/index> \
  --fee-recipient <ETHEREUM_ADDRESS> \
  --rpc-url https://rpc.tempo.xyz
```

```bash [Testnet]
tempo consensus set-validator-fee-recipient <address/pubkey/index> \
  --fee-recipient <ETHEREUM_ADDRESS> \
  --rpc-url https://rpc.testnet.tempo.xyz
```
:::

### Choose the validator fee token

From [v1.12.0](https://github.com/tempoxyz/tempo/releases/tag/v1.12.0), `tempo consensus set-validator-token` lets you select the token your validator receives fees in. It must be a USD-denominated [TIP-20](https://tempo.com/developers/docs/protocol/tip20/overview) token, Tempo's stablecoin token standard. The command calls the [FeeManager](https://tempo.com/developers/docs/protocol/fees/spec-fee-amm#key-functions), the fee contract at `0xfeec000000000000000000000000000000000000` that collects fees and stores fee token preferences. It sets the preference for the **transaction sender**. Submit from your validator's fee-recipient address, which can differ from the validator operator address.

List the tokens the CLI knows as verified on your network. This needs no signer:

:::code-group
```bash [Mainnet]
tempo consensus set-validator-token --list --rpc-url https://rpc.tempo.xyz
```

```bash [Testnet]
tempo consensus set-validator-token --list --rpc-url https://rpc.testnet.tempo.xyz
```
:::

Preview a selection using a token address, symbol, or name from the list:

```bash
tempo consensus set-validator-token <TOKEN> \
  --rpc-url https://rpc.tempo.xyz \
  --dry-run
```

For a raw token address, `--no-fetch-verified-tokens` skips the verified-token list lookup. The FeeManager still validates the token onchain.

The token must be a deployed TIP-20 token with currency `USD`. The FeeManager rejects a preference change in a block whose fee recipient is the caller, such as a block your own validator proposes. Send the transaction again so it lands in a block another validator proposes. This command changes the preferred token, not the fee-recipient address; see [Update the fee recipient](https://tempo.com/developers/docs/guide/node/validator-lifecycle#update-the-fee-recipient) to change that address.

### Claim validator fees

Validator fees accumulate in the FeeManager, one balance per token, until someone calls `distributeFees`. The call sends the balance for one token to your fee-recipient address. Any funded account can submit it. The example uses a Foundry keystore account:

```bash
cast send 0xfeec000000000000000000000000000000000000 \
  "distributeFees(address,address)" \
  "<FEE_RECIPIENT_ADDRESS>" "<TOKEN_ADDRESS>" \
  --rpc-url https://rpc.tempo.xyz \
  --account "<KEYSTORE_ACCOUNT>"
```

### Transfer validator ownership

Move your validator entry to a new validator operator address. Submit with the current operator address's signer:

:::code-group
```bash [Mainnet]
tempo consensus transfer-validator-ownership <address/pubkey/index> \
  --rpc-url https://rpc.tempo.xyz \
  --new-private-key <PATH_TO_NEW_VALIDATOR_PRIVATE_KEY>
```

```bash [Testnet]
tempo consensus transfer-validator-ownership <address/pubkey/index> \
  --rpc-url https://rpc.testnet.tempo.xyz \
  --new-private-key <PATH_TO_NEW_VALIDATOR_PRIVATE_KEY>
```
:::

The CLI derives the new operator address from the key file at `--new-private-key`. That new address must not already be used by another active validator.

### Deactivate your validator

Deactivate your validator to remove it from the active set, the validators registered as active in ValidatorConfig V2.

:::warning[Do not shut down your node immediately after deactivating]
Your validator remains a dealer in the committee for one more epoch after the epoch in which you deactivate, distributing key shares to the next committee. A failed DKG round extends that. Shutting it down early will degrade network liveness. See the [exit timeline](https://tempo.com/developers/docs/guide/node/validator-lifecycle#exit-timeline) below.
:::

:::code-group
```bash [Mainnet]
tempo consensus deactivate-validator <address/pubkey/index> \
  --rpc-url https://rpc.tempo.xyz
```

```bash [Testnet]
tempo consensus deactivate-validator <address/pubkey/index> \
  --rpc-url https://rpc.testnet.tempo.xyz
```
:::

#### Exit timeline

Deactivation isn't instant. Your validator leaves over two epochs, counted from epoch E, the epoch in which the deactivation transaction lands. The table uses the fields from [validator lookup](https://tempo.com/developers/docs/guide/node/validator-status#look-up-your-validator):

| Epoch | State | `is_dkg_dealer` | `is_dkg_player` | `in_committee` |
|-------|-------|:---------------:|:---------------:|:--------------:|
| **E** (deactivation) | Active | `true` | `true` | `true` |
| **E+1** | Exiting | `true` | `false` | `true` |
| **E+2** | Exited | `false` | `false` | `false` |

Keep your node running until validator lookup shows `in_committee: false`. At that point, it's safe to shut down the node.
