Operators Guide

For stalled heights, peer failures, or state mismatches, start with Troubleshoot a Node. Record the binary revision and failing height before changing state.

Choose the Node Profile

Full nodes serve queries and retain recent history. Archive nodes preserve available historical state. Validators use a signing profile with public application APIs disabled, and seed nodes serve peer discovery. Hardware sizing depends on traffic, retained history, and the selected stores.

Use Configuration to choose a node profile and its enabled services. Validator participation also depends on on-chain registration and the active set.

HPX Node Management

HPX manages a native paxd systemd service and verifies installation artifacts against its checksum manifest. The default distribution origin is https://node.hyperpaxeer.com.

From the monorepo root, inspect and run the checked-out bootstrap script:

less paxeer-network/hpx/get-hpx.sh
sudo bash paxeer-network/hpx/get-hpx.sh
HPX_TYPE=fullnode hpx setup

Select HPX_TYPE=validator for the validator setup flow. The selected artifact set includes the binary, architecture-specific Wasm runtimes, genesis, and configuration. Use the selected mirror's manifest to confirm the release and artifact checksums.

hpx status
hpx info
hpx logs
hpx peers show
hpx statesync
hpx help

hpx peers refresh changes the peer configuration; hpx register announces the node to the registry. Use hpx update as a planned version change after checking network compatibility.

Local Development Cluster

From paxeer-network/:

make docker-cluster-start
make docker-cluster-start-monitoring

The repository provides separate local cluster and monitoring targets. See Docker for compose services and generated paths.

Validator Accounts and Keys

The operator account submits staking and governance transactions. The consensus key signs blocks. Use an existing operator account, or create one with the following commands:

paxd keys add operator
paxd keys show operator -a
paxd keys show operator --bech val -a
paxd tendermint show-validator

A pax1… account address, paxvaloper1… validator address, and consensus public key are distinct arguments. Use the form required by each command.

Register a Validator

After the node is synchronized and the operator is funded, register it with create-validator. This example uses one PAX in base units. Choose your stake, moniker, and commission settings, taking the network's active validator set into account.

paxd tx staking create-validator \
  --amount=1000000uhpx \
  --pubkey="$(paxd tendermint show-validator)" \
  --moniker="My Validator" \
  --chain-id=hyperpax_125-1 \
  --commission-rate="0.10" \
  --commission-max-rate="0.20" \
  --commission-max-change-rate="0.01" \
  --min-self-delegation="1" \
  --gas=auto \
  --gas-adjustment=1.5 \
  --gas-prices=0.02uhpx \
  --from=operator

--min-self-delegation is expressed in base units. Set gas prices for the connected network. Choose either --gas-prices with a gas limit or an explicit --fees amount.

Inspect Validator State

paxd query staking validator "$(paxd keys show operator --bech val -a)"
paxd query staking delegations-to "$(paxd keys show operator --bech val -a)"
paxd query slashing signing-info "$(paxd tendermint show-validator)"
paxd query staking params
paxd query slashing params

The staking module also exposes edit-validator, delegate, redelegate, and unbond. paxd tx slashing unjail is subject to the keeper's eligibility checks; it cannot reverse permanent tombstoning.

Monitoring

curl -sS http://127.0.0.1:26657/status | jq '.result.sync_info'
curl -sS http://127.0.0.1:26657/net_info | jq '.result.n_peers'
journalctl -u paxd -f

Enable the configured Prometheus listener as shown in Configuration. Consensus metrics include block height, last-signed height, missed-block gauges, and syncing state. Build alerts from the emitted metric names and choose thresholds for your workload. Treat missed-block values as gauges.

Peer and Signer Configuration

Use bootstrap-peers, persistent-peers, and private-peer-ids under [p2p]. The peer ID can be read with paxd tendermint show-node-id. Keep signer access separate from public query services.

Remote signers connect through the configured [priv-validator] socket or gRPC interface. For a hardware-backed signer, use an integration compatible with that interface and verify signing before activating the validator.

Backup and Recovery

Default paths are relative to ~/.paxeer and can be overridden. Stop the node before replacing its stores. Preserve the key and last-sign state together and ensure the original signer is offline before activating a replacement. Never start a second active signer with the same validator key.

For snapshot recovery, verify the archive revision, checksum, backend, and layout before extraction. Reserve unsafe-reset-all for a planned state reset with complete backups. Use retention settings for routine pruning and paxd rollback for supported stopped-node state reconciliation.

Planned Upgrades

Match the network's upgrade plan and the release revision before replacing a binary. Record the installed version, preserve the previous binary and required state, stop the service, install the compatible release, and confirm synchronization after restart. Check the release's upgrade and snapshot compatibility requirements before installation.

Governance upgrade proposals use the registered software-upgrade command. Expedited proposal support uses --is-expedited; query current deposit and voting parameters before submitting.