Paxeer XDocs
How do I run a Paxeer X node?

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 nodebashReady
    paxd init my-node --chain-id hyperpax_125-1 --mode full
    From Run a Node › Initialize Node
  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.

    Check a state-sync checkpointbashReady
    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'
    From Run a Node › State Sync
  4. Start the node

    Start paxdbashReady
    paxd start --home "$HOME/.paxeer"
    From Run a Node › Start Node
  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 peersbashReady
    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'
    From Run a Node › Verify Synchronization
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 covers registration and last-sign-state handling.

Paxeer chain node
chain-node
nodechanged in this release
Directory
daemon/paxd
Build
make build
Build output
build/paxd
Health check
paxd status
Ports
2665626657854585461317
Configuration
node/params/config.go and docs/release/7.0.0-validator-runbook.md
Used by
LayerX kernel hostEpoch moduleEVM moduleLaunchpad moduleLayerX agent moduleLayerX anchor moduleLayerX auth moduleLayerX bridge moduleLayerX chains moduleLayerX custody moduleLayerX exchange moduleLayerX governance moduleLayerX ledger moduleLayerX pay moduleMint moduleOracle modulePerpetuals modulePrice feed moduleEmbedded sequencer moduleSpot moduleStore moduleToken factory moduleXWeb moduleAddress binding precompilesBank precompileCommon token precompilesDistribution precompilesFee token precompileGovernance precompileIBC precompilesJSON precompileLaunchpad precompilesLayerX agent precompilesLayerX anchor precompileLayerX auth precompileLayerX bridge precompileLayerX chains precompileLayerX custody precompileLayerX exchange precompileLayerX ledger precompileLayerX pay precompileLayerX programs precompileLayerX verify precompileOracle precompileP-256 precompilePerpetuals precompilePointer precompilePointer view precompilePrice feed precompileSolo precompileSpot precompilesStaking precompileWasm precompileXWeb precompileHosted gatewayExplorer backendAgent daemonInterop workspaceBridge relayerLaunchpad indexerWallet gatewayHuman serviceBridge deployment serviceLaunchpad service workspacePlatform hosted servicesInference peerLaunchpad web applicationNames applicationPaxeer Xtrades applicationWallet applicationLaunchpad web applicationWallet applicationInference peerNames applicationWallet SDKCosmos TypeScript SDKNames SDKAgent TypeScript SDKWallet SDKCosmos TypeScript SDKNames SDKRelease toolsPaxctl operator CLILayerX developer CLILoad test toolNode bring-up toolRelease rollback toolBackup and monitoring toolsBackup and restore toolsMonitoring stackPaxeer load generatorCosmovisor supervisor

Pages: /run-node · System map entry

Ask next

5 blocks are shown verbatim from the documentation, and every identifier in the text was found there.

Reviewed answer
Run a Paxeer X node · Paxeer X Docs