Skip to main content

Node Commands

Reference for qorechaind commands used to initialize, configure, and operate a QoreChain node.

note

QoreChain runs two networks: the qorechain-vladi mainnet (live since 7 June 2026 on chain version v3.1.85) and the qorechain-diana testnet. Pass the appropriate --chain-id for the network you intend to join — the examples below target the testnet; use --chain-id qorechain-vladi for mainnet.


init

Initialize a new node with the given moniker.

qorechaind init <moniker> --chain-id qorechain-diana
FlagTypeDescription
--chain-idstringChain identifier (required)
--homestringNode home directory (default: ~/.qorechaind)
--overwriteboolOverwrite existing genesis and config files

Creates the directory structure under --home with config/, data/, and an initial genesis.json.


start

Start the node and begin syncing or producing blocks.

qorechaind start [flags]
FlagTypeDescription
--homestringNode home directory
--minimum-gas-pricesstringMinimum gas prices to accept (e.g., 0.001uqor)
--pruningstringPruning strategy: default, nothing, everything
--halt-heightuintStop the node at this block height
--halt-timeuintStop the node at this Unix timestamp
--log_levelstringLog verbosity: info, debug, warn, error
--traceboolEnable full stack trace on errors

version

Print the qorechaind binary version and build information.

qorechaind version

Use --long for extended build details including Go version, commit hash, and build tags:

qorechaind version --long

status

Query the running node for its current status, including sync state, latest block height, and consensus information.

qorechaind status
FlagTypeDescription
--nodestringRPC endpoint (default: tcp://localhost:26657)

Returns JSON with node_info, sync_info, and validator_info sections.


config

Read or write values in the node configuration.

Set a Configuration Value

qorechaind config set <key> <value>

Get a Configuration Value

qorechaind config get <key>

Common configuration keys include chain-id, keyring-backend, output, and node.


keys

Manage local keyring for signing transactions.

Add a New Key

qorechaind keys add <name> [flags]
FlagTypeDescription
--keyring-backendstringBackend: os, file, test
--algostringKey algorithm: secp256k1 (default), ed25519
--recoverboolRecover key from mnemonic
--multisigstringComma-separated list of keys for multisig
--multisig-thresholduintMinimum signatures required

List All Keys

qorechaind keys list --keyring-backend <backend>

Show Key Details

qorechaind keys show <name> [flags]
FlagTypeDescription
--bechstringOutput format: acc, val, cons
--addressboolShow address only
--pubkeyboolShow public key only

Delete a Key

qorechaind keys delete <name> --keyring-backend <backend>

Export a Key (Armor-Encrypted)

qorechaind keys export <name>

Import a Key

qorechaind keys import <name> <keyfile>

genesis

Manage the genesis file.

Add a Genesis Account

qorechaind genesis add-genesis-account <address> <coins> [flags]
FlagTypeDescription
--vesting-amountstringVesting amount
--vesting-end-timeintVesting end time (Unix timestamp)

Create a Genesis Transaction

qorechaind genesis gentx <key-name> <stake-amount> [flags]
FlagTypeDescription
--chain-idstringChain identifier
--monikerstringValidator moniker
--commission-ratestringInitial commission rate
--commission-max-ratestringMaximum commission rate

Collect Genesis Transactions

qorechaind genesis collect-gentxs

Validate the Genesis File

qorechaind genesis validate-genesis

Consensus Engine

These subcommands interact with the QoreChain Consensus Engine layer.

Show Validator Key

qorechaind comet show-validator

Outputs the consensus public key in JSON format. Used to verify validator identity.

Show Node ID

qorechaind comet show-node-id

Outputs the P2P node identifier (hex-encoded). Used for persistent peer configuration.


export

Export the current chain state as a JSON genesis file. Useful for chain upgrades or snapshots.

qorechaind export [flags]
FlagTypeDescription
--for-zero-heightboolPrepare export for restarting at height 0
--heightintExport state at a specific block height
--homestringNode home directory

rollback

Roll back the chain state by one block. Useful for recovering from a consensus failure.

qorechaind rollback [flags]
FlagTypeDescription
--hardboolRemove the last block from the block store as well
--homestringNode home directory

This command rolls back both the application state and the consensus state. Use with caution, as it cannot be undone.