All transaction commands follow the pattern:
qorechaind tx <module> <command> [args] [flags]
Common flags apply to every tx subcommand:
Name or address of the signing key
Chain identifier (default: from config)
Transaction fees (e.g., 500uqor)
Gas limit or auto for estimation
Gas multiplier when using auto (default: 1.0)
Keyring backend: os, file, test
RPC endpoint (default: tcp://localhost:26657)
Transfer tokens from one account to another.
qorechaind tx bank send <from_address> <to_address> <amount> [flags]
create-validator
Create a new validator on the network.
Self-delegation amount (e.g., 1000000uqor)
Validator consensus public key (JSON)
Initial commission rate (e.g., 0.10)
--commission-max-change-rate
Maximum daily commission change rate
Minimum self-delegation required
Edit an existing validator's description or commission.
Delegate tokens to a validator.
Move delegation from one validator to another.
Unbond tokens from a validator.
withdraw-all-rewards
Withdraw all pending staking rewards.
withdraw-rewards
Withdraw rewards from a specific validator.
Also withdraw validator commission
submit-proposal
Submit a governance proposal.
The proposal file is a JSON document specifying the proposal type, title, description, and any messages to execute.
Vote on an active proposal.
Vote options: yes, no, abstain, no_with_veto.
Add a deposit to a proposal.
Register a post-quantum public key for an account.
register-key-v2
Register a PQC key with extended metadata and attestation.
TEE attestation data (hex)
Additional key metadata (JSON)
Migrate an existing classical key to a hybrid PQC key pair.
Lock QOR tokens into an xQORE governance staking position.
Lock duration (e.g., 30d, 90d, 180d)
Unlock xQORE back to QOR. Early unlock may incur penalties depending on the penalty tier.
Initiate a bridge deposit from an external chain.
Recipient address on QoreChain
Initiate a bridge withdrawal to an external chain.
Send a cross-VM message between execution environments (EVM, CosmWasm, SVM).
Source VM: evm, cosmwasm, svm
Gas limit for the cross-VM execution
Manually process pending cross-VM messages (operator command).
Deploy a BPF program to the SVM runtime.
Optional program ID (base58)
Execute an instruction on a deployed SVM program.
Comma-separated account pubkeys for the instruction
Create a new SVM account with allocated data space.
Owner program (base58, default: system program)
register-sidechain
Register a new sidechain layer.
Blocks between mandatory anchor submissions
register-paychain
Register a new payment channel layer.
Submit a state anchor for a registered layer.
Route a transaction to the optimal layer.
Force routing to a specific layer
update-layer-status
Update the operational status of a layer (operator only).
Status values: active, paused, draining.
challenge-anchor
Submit a fraud challenge against a state anchor.
Register a new rollup with the Rollup Development Kit.
optimistic, zk, pessimistic, sovereign
Preset: defi, gaming, nft, social, general
Enable native data availability
Submit a settlement batch for a rollup.
challenge-batch
Submit a fraud challenge against a settlement batch (optimistic rollups).
Manually finalize a batch that has passed the challenge window.
Pause a rollup (operator only).
Resume a paused rollup (operator only).
Permanently stop a rollup and release its stake (operator only).
submit-btc-checkpoint
Submit a BTC checkpoint for an epoch.
Restake BTC via the Babylon integration.
Bitcoin transaction hash as proof
abstractaccount
Create an abstract account with programmable spending rules.
JSON file defining spending rules
update-spending-rules
Update the spending rules for an existing abstract account.
Set the RL agent operational mode (governance only).
Mode values: 0 (off), 1 (observe), 2 (suggest), 3 (auto).
Resume the RL agent after a circuit breaker trip.
Update the RL agent policy configuration (governance only).
update-reward-weights
Update the reward weight configuration for the RL agent.
Weight for throughput reward
Weight for latency reward
Weight for security reward