<!-- Question: How do I run a Paxeer X node? -->
<!-- Source: https://docs.paxeer.app/a/run-a-node (reviewed answer, corpus 837d42000759) -->

# Run a Paxeer X node

Initialise `paxd` for the role you want, install the network's verified genesis and peers, start it, then confirm it has synchronised before you send it traffic.

- **Node binary:** paxd
- **Default home:** ~/.paxeer
- **Peer port:** 26656 (Default)
- **Consensus RPC port:** 26657 (Default)

1. **Initialise the node for its role**

   `--mode` selects the profile. The roles are full, archive, validator and seed. Validator operators select `--mode validator` before configuring the signer and peer topology.
   
   **Initialise a full node**
   
   ```sh
   paxd init my-node --chain-id hyperpax_125-1 --mode full
   ```

2. **Install genesis and peers**

   Place the verified network genesis at `~/.paxeer/config/genesis.json` and confirm its chain ID and checksum. Set `bootstrap-peers` and `persistent-peers` under `[p2p]` in `config.toml`, using the network's entries in `node-id@host:port` form.

3. **Choose how the node catches up**

   Replay blocks, state sync from a recent snapshot, or restore a filesystem snapshot. State sync needs at least two RPC servers and a trusted checkpoint within the trust period, and it starts only when the node has no local application state. See [Genesis and Peers](https://docs.paxeer.app/run-node#genesis-and-peers).
   
   **Check a state-sync checkpoint**
   
   ```sh
   curl -sS "$TM_RPC_URL/status" | jq '.result.sync_info'
   curl -sS "$TM_RPC_URL/block?height=$TRUST_HEIGHT" | jq '.result.block.header, .result.block_id.hash'
   ```

4. **Start the node**

   **Start paxd**
   
   ```sh
   paxd start --home "$HOME/.paxeer"
   ```

5. **Verify synchronisation**

   Confirm the expected chain identity, an advancing block height and completed synchronisation before directing application traffic to the node.
   
   **Check sync status and peers**
   
   ```sh
   paxd status --node "$TM_NODE_URL"
   curl -sS "$TM_RPC_URL/status" | jq '.result.sync_info'
   curl -sS "$TM_RPC_URL/net_info" | jq '.result.n_peers'
   ```

> **Validators: protect the signing key:** The consensus signing key is separate from the operator account. When you restore a snapshot, preserve the validator signing key and its last-sign state. The [Operators Guide](https://docs.paxeer.app/operators) covers registration and last-sign-state handling.

**Paxeer chain node** (`chain-node`, node)

| Field | Value |
| --- | --- |
| Directory | `daemon/paxd` |
| Build | `make build` |
| Output | `build/paxd` |
| Configuration | node/params/config.go and docs/release/7.0.0-validator-runbook.md |
| Ports | 26656, 26657, 8545, 8546, 1317 |
| Health check | `paxd status` |
| Depends on | none |

**Read next**

- [Configuration](https://docs.paxeer.app/configuration): The current paxd configuration files, node modes, RPC settings, and storage controls.
- [Operators Guide](https://docs.paxeer.app/operators): Manage paxd nodes, whose LayerX kernel executes and orders transactions and builds blocks, and the validators that check and commit them.
- [Troubleshoot a Node](https://docs.paxeer.app/node-troubleshooting): Diagnose Paxeer X sync stalls, peer failures, RPC errors, database locks, and AppHash mismatches before changing node state.
- [Docker Development](https://docs.paxeer.app/docker): Local Docker clusters, state-sync RPC nodes, and monitoring for Paxeer X development and testing.

---

Sources: [Run a Node › Initialize Node](https://docs.paxeer.app/run-node#initialize-node) · [Run a Node › State Sync](https://docs.paxeer.app/run-node#state-sync) · [Run a Node › Start Node](https://docs.paxeer.app/run-node#start-node) · [Run a Node › Verify Synchronization](https://docs.paxeer.app/run-node#verify-synchronization) · [Run a Node](https://docs.paxeer.app/run-node) · [Run a Node › Genesis and Peers](https://docs.paxeer.app/run-node#genesis-and-peers) · [Operators Guide](https://docs.paxeer.app/operators)
