Skip to main content

Token Operations

This guide covers the QOR token, how to send and receive tokens, query balances, and understand the fee distribution model on QoreChain.

note

The commands below use the qorechain-diana testnet (EVM chain ID 9800). Mainnet (qorechain-vladi, EVM chain ID 9801) has been live since 7 June 2026 running chain version v3.1.77 — substitute the mainnet chain ID and endpoints from the Connecting to Mainnet page when transacting on mainnet.

Token Information

PropertyValue
Display DenominationQOR
Base Denominationuqor
Conversion1 QOR = 1,000,000 uqor (10^6)
Chain IDqorechain-vladi (mainnet) / qorechain-diana (testnet)
Bech32 Prefixqor (e.g., qor1abc...xyz)

All on-chain amounts are denominated in uqor. When submitting transactions, always specify amounts in uqor.

Sending Tokens

To transfer QOR tokens from one account to another:

qorechaind tx bank send <from_address> <to_address> <amount>uqor \
--chain-id qorechain-diana \
--fees 500uqor

Example: Send 5 QOR (5,000,000 uqor) to another address:

qorechaind tx bank send qor1sender... qor1recipient... 5000000uqor \
--chain-id qorechain-diana \
--fees 500uqor

You can also use a key name instead of a raw address for the sender:

qorechaind tx bank send mykey qor1recipient... 5000000uqor \
--chain-id qorechain-diana \
--fees 500uqor

Querying Balances

Check the balance of any account:

qorechaind query bank balances <address>

Example:

qorechaind query bank balances qor1abc...xyz

Sample output:

balances:
- amount: "15000000"
denom: uqor
pagination:
next_key: null
total: "0"

This indicates the account holds 15 QOR (15,000,000 uqor).

Fee Structure

Transaction fees on QoreChain are distributed across five destinations to align network incentives:

DestinationSharePurpose
Validators37%Rewards block producers and secures the network
Burned30%Permanently removed from supply, creating deflationary pressure
Treasury20%Funds protocol development and ecosystem grants
Stakers10%Distributed proportionally to all delegators
Light Nodes3%Rewards light-node operators that serve network data

Burn Channels

QoreChain implements a multi-channel burn mechanism. QOR tokens are permanently removed from circulation through 10 distinct channels:

ChannelDescription
tx_feeThe 30% burn portion of every transaction fee
governance_penaltyBurned when governance proposals fail to reach quorum or are vetoed
slashing_burnBurned portion of slashed validator stakes
bridge_feeFee burned on cross-chain bridge transfers
spam_deterrentAdditional burn applied to flagged spam transactions
epoch_excessExcess emissions beyond target burned at epoch boundaries
manual_burnCommunity-initiated token burns via governance proposal
contract_callbackFees burned on smart contract callback executions
cross_vm_feeBurned when executing cross-VM (e.g., EVM to CosmWasm) calls
rollup_create1% of the minimum stake burned when deploying a new rollup

You can query the total burned amount across all channels:

qorechaind query bank total --denom uqor

Tips

caution

Always double-check recipient addresses before sending tokens. Transactions on QoreChain are irreversible.

tip
  • Use the --dry-run flag to simulate a transaction without broadcasting it.
  • Use --gas auto to let the node estimate the required gas for your transaction.
  • The minimum fee for a standard transfer is 500 uqor.