Reference for qorechaind commands used to initialize, configure, and operate a QoreChain node.
Initialize a new node with the given moniker.
qorechaind init <moniker> --chain-id qorechain-diana
Chain identifier (required)
Node home directory (default: ~/.qorechaind)
Overwrite existing genesis and config files
Creates the directory structure under --home with config/, data/, and an initial genesis.json.
Start the node and begin syncing or producing blocks.
qorechaind start [flags]
Minimum gas prices to accept (e.g., 0.001uqor)
Pruning strategy: default, nothing, everything
Stop the node at this block height
Stop the node at this Unix timestamp
Log verbosity: info, debug, warn, error
Enable full stack trace on errors
Print the qorechaind binary version and build information.
Use --long for extended build details including Go version, commit hash, and build tags:
Query the running node for its current status, including sync state, latest block height, and consensus information.
RPC endpoint (default: tcp://localhost:26657)
Returns JSON with node_info, sync_info, and validator_info sections.
Read or write values in the node configuration.
Set a Configuration Value
Get a Configuration Value
Common configuration keys include chain-id, keyring-backend, output, and node.
Manage local keyring for signing transactions.
Key algorithm: secp256k1 (default), ed25519
Recover key from mnemonic
Comma-separated list of keys for multisig
Minimum signatures required
Show Key Details
Output format: acc, val, cons
Export a Key (Armor-Encrypted)
Manage the genesis file.
Add a Genesis Account
Vesting end time (Unix timestamp)
Create a Genesis Transaction
Collect Genesis Transactions
Validate the Genesis File
Consensus Engine
These subcommands interact with the QoreChain Consensus Engine layer.
Show Validator Key
Outputs the consensus public key in JSON format. Used to verify validator identity.
Outputs the P2P node identifier (hex-encoded). Used for persistent peer configuration.
Export the current chain state as a JSON genesis file. Useful for chain upgrades or snapshots.
Prepare export for restarting at height 0
Export state at a specific block height
Roll back the chain state by one block. Useful for recovering from a consensus failure.
Remove the last block from the block store as well
This command rolls back both the application state and the consensus state. Use with caution, as it cannot be undone.
