Skip to main content

Staking and Delegation

This guide covers how to delegate QOR tokens to validators, redelegate between validators, unbond your stake, claim rewards, and understand which parts of QoreChain's staking design are live today.

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 and runs release v3.2.7 (applied on 12 November 2026; v3.2.6 on 4 November, v3.2.5 on 29 October and v3.2.4 on 23 October); the testnet has run v3.2.8 since 12 November 2026 (v3.2.7 from 6 November, v3.2.6 from 27 October). Substitute the mainnet chain ID and endpoints from the Connecting to Mainnet page when staking on mainnet.

Sign with tx pqc cosign

Mainnet and testnet require a hybrid post-quantum signature on every Cosmos-lane transaction, so the commands on this page do not broadcast as written. Add --generate-only > tx.json to a command, then run qorechaind tx pqc cosign tx.json --from mykey --pqc-key mypqc --chain-id <chain-id>. See Hybrid signing. QoreX and the Dashboard do this signing for you.

Is there a lock-in period?​

For ordinary delegation, no — there's no term to pick, because staking isn't sold in fixed durations here the way it often is on an exchange. Delegating stays active with rewards flowing from the next block, for as long as you want, until you choose to undelegate; there's nothing expiring and nothing to renew. The 21-day unbonding period you'll see referenced throughout this guide is not a lock-in you agree to up front — it only starts once you ask to undelegate, and only applies to the QOR you're taking out. Moving a delegation between validators (redelegate) skips that wait entirely, since the stake never leaves the bonded pool. The "loyalty" term in the bonding curve further down is part of QoreChain's design but is not applied by the live chain today, so how long you stay delegated does not change your reward rate. An optional, time-locked form of staking is available on mainnet since v3.2.4 (23 October 2026) and on the testnet since 19 October 2026; you only get a lock if you create one. See Time-locked staking (v3.2.4).

This describes current mainnet behavior, not a permanent guarantee — a minimum staking period is something governance could introduce in the future, the same way any other staking parameter on this page can change by vote. If that ever happens, the wallet will show the resulting wait (any minimum plus the 21-day unbonding) before you confirm a delegation, and this page will be updated to match.


Delegating Tokens​

Delegate QOR to a validator to take part in network security. Delegators receive a share of the rewards the validator earns, less the validator's commission:

qorechaind tx staking delegate <validator_address> <amount>uqor \
--from mykey \
--chain-id qorechain-diana \
--gas 400000 --fees 40000uqor

Example: Delegate 100 QOR to a validator:

qorechaind tx staking delegate qorvaloper1abc...xyz 100000000uqor \
--from mykey \
--chain-id qorechain-diana \
--gas 400000 --fees 40000uqor

Redelegating​

Move your delegation from one validator to another without waiting for the unbonding period:

qorechaind tx staking redelegate <source_validator> <destination_validator> <amount>uqor \
--from mykey \
--chain-id qorechain-diana \
--gas 400000 --fees 40000uqor

Example:

qorechaind tx staking redelegate qorvaloper1src... qorvaloper1dst... 50000000uqor \
--from mykey \
--chain-id qorechain-diana \
--gas 400000 --fees 40000uqor

Redelegating has no penalty and no lock of its own — the stake never leaves the bonded pool, never stops earning, and takes effect immediately. It is not subject to the 21-day unbonding period at all; that applies only to unbond. One standard staking rule applies: stake you have just moved to a validator cannot be redelegated again from that validator until the first move has matured (21 days); you can still unbond it or redelegate your other stake in the meantime.

The real limit is a count, not a cooldown

A delegator can have at most 7 simultaneous in-flight redelegation entries for the exact same (delegator, source validator, destination validator) route — each entry clears on its own as it matures, freeing a slot. This is a ceiling normal use essentially never reaches, not a general "wait before you can redelegate again" rule.


Unbonding​

Withdraw your delegated tokens from a validator. Unbonding takes 21 days to complete, during which the tokens do not earn rewards and cannot be transferred.

qorechaind tx staking unbond <validator_address> <amount>uqor \
--from mykey \
--chain-id qorechain-diana \
--gas 400000 --fees 40000uqor

Example:

qorechaind tx staking unbond qorvaloper1abc...xyz 25000000uqor \
--from mykey \
--chain-id qorechain-diana \
--gas 400000 --fees 40000uqor

After the 21-day unbonding period (1,814,400 seconds), tokens are automatically returned to your account. A delegator can have at most 7 simultaneous unbonding entries per validator.


Claiming Rewards​

Withdraw all accumulated staking rewards from every validator you have delegated to:

qorechaind tx distribution withdraw-all-rewards \
--from mykey \
--chain-id qorechain-diana \
--gas 400000 --fees 40000uqor

To withdraw rewards from a specific validator only:

qorechaind tx distribution withdraw-rewards <validator_address> \
--from mykey \
--chain-id qorechain-diana \
--gas 400000 --fees 40000uqor

Staking rewards are funded from two sources: the protocol's capped emission budget (see Tokenomics for the current amount per epoch and the cap, both set by governance — most recently proposal 10 on 19 October 2026) and the staker share of every transaction fee (paid out as a normal staking reward since the v3.2.0 upgrade; see the stranded staker share). Rewards depend on the validator's commission and on network activity, and are not guaranteed.


Time-locked staking (v3.2.4)​

When this applies

Release v3.2.4 adds an optional time-locked staking module, x/stakingtier. It has been live on the qorechain-diana testnet since 19 October 2026 and on mainnet since 23 October 2026 (applied at height 3,742,566 by governance proposal 13); mainnet has run v3.2.5 since 29 October 2026, v3.2.6 since 4 November 2026 and v3.2.7 since 12 November 2026, which keep it unchanged apart from the undelegation check described below and the APR routes added in v3.2.7. Locking is available as an option and ordinary delegation stays lock-free (see above). The mechanism below was checked against the live mainnet and testnet parameters on 23 October 2026.

A delegator can commit part of an existing delegation to a validator for a fixed term of 3, 6 or 12 months. Terms and amounts are chain parameters; read the current ones from GET /qorechain/stakingtier/v1/params rather than from this page.

  • Locking is optional. Ordinary delegation, redelegation and unbonding work exactly as described on this page. Only the locked amount is restricted: while a lock is open it cannot be undelegated or redelegated, and this holds for every route (transaction, authz, group, contract, governance).
  • Minimum lock of 10 QOR, and at most 16 open locks per delegator.
  • Early unlock is allowed: it ends the lock, forfeits whatever lock reward has not been paid, and burns a penalty taken from the locked amount (5% in the current parameters, recorded under the staking_tier_penalty burn source); the rest stays delegated and unlocked.
  • Slashing applies to a locked delegation like any other; the lock shrinks with the delegation.
  • Claiming. A lock earns an additional per-epoch reward component set by the module parameters; it is paid when you claim it, not automatically. This page does not quote rates: read params for the live settings.
  • At expiry the lock is released and the delegation continues as an ordinary one.

The commands are available through the command line and the REST routes GET /qorechain/stakingtier/v1/params, /locks/{holder} and /pool; from release v3.2.7 (testnet since 6 November 2026, mainnet since 12 November 2026) there are also GET /qorechain/stakingtier/v1/apr (a base rate plus the tier bonuses) and GET /qorechain/stakingtier/v1/apr/{delegator}, which show what the module currently computes. These are readings of the current settings, not a guaranteed or promised return: the base rate depends on fees and funding and can be zero, and the bonuses can be changed by governance. Amounts in the commands are an integer number of uqor (1 QOR = 1,000,000 uqor).

qorechaind tx stakingtier lock <validator_address> <amount_in_uqor> <months> --from mykey \
--chain-id qorechain-diana --gas 400000 --fees 40000uqor --generate-only > tx.json
qorechaind tx stakingtier unlock-early <lock_id> --from mykey --chain-id qorechain-diana \
--gas 400000 --fees 40000uqor --generate-only > tx.json
qorechaind tx stakingtier claim --from mykey --chain-id qorechain-diana \
--gas 400000 --fees 40000uqor --generate-only > tx.json
qorechaind query stakingtier locks <holder_address>

The chain ID above is the testnet's; use qorechain-vladi on mainnet. As on the rest of this page, sign each generated transaction with tx pqc cosign.

Using time-locked staking​

Steps. (1) Delegate to a validator as usual. (2) Run tx stakingtier lock for that validator with an amount (at least 10 QOR) and a term of 3, 6 or 12 months, then cosign and broadcast. (3) Read the result with GET /qorechain/stakingtier/v1/locks/{holder} or qorechaind query stakingtier locks <holder_address>; each lock has an id. (4) Claim with tx stakingtier claim whenever you want the lock reward. (5) At the end of the term the lock releases by itself; to leave sooner use tx stakingtier unlock-early <lock_id> and accept the penalty.

Where it works, checked on 27 October 2026 (the v3.2.6 row for mainnet comes from the release notes and the 4 November 2026 upgrade; the parameters below were re-read on mainnet on 4 November 2026). Before v3.2.6, mainnet refused the undelegation only when the transaction ran, through the staking message gate.

Mainnet qorechain-vladi (v3.2.7)Testnet qorechain-diana (v3.2.8)
Module liveYes, since height 3,742,566Yes, since v3.2.4 (height 8,337,253)
Open locksNone yet3 test locks
Undelegating locked stakeRefused by the mempool before any fee is charged (since v3.2.6, applied on mainnet on 4 November 2026)Refused by the mempool before any fee is charged

Both networks answer GET /qorechain/stakingtier/v1/params with the same settings: three terms, a 10 QOR minimum (min_lock_amount "10000000" uqor), an early-unlock penalty of 500 basis points (5%) and enabled: true. The response also carries the bonus settings in basis points; this manual does not quote them, because a bonus is not a promised return and the settings can be changed by governance. GET /qorechain/stakingtier/v1/pool shows the pool that pays lock rewards.

Clients. The command line (above) and @qorechain/sdk (0.10.0 or later; 0.14.0 is current), which has the composers lockDelegation, unlockEarly and claimBonus and the reads fetchStakingTierParams, fetchStakingLocks and fetchStakingTierPool (see SDK install). No published version of QoreX or the dashboard has a lock screen today, so locking on mainnet is done with the CLI or the SDK.

Do not mix it up with xQORE staking, which is a designed mechanism that is not live, or with the Triple-Pool classification below, which does not change what you receive.


Triple-Pool Classification (design status)​

QoreChain's design includes a Triple-Pool model that would classify validators into three pools by reputation and delegation level, with a weighted share of block rewards per pool:

PoolEntry CriteriaDesign Reward Weight
RPoS (Reputation Proof of Stake)Reputation score >= 70th percentile AND stake >= median40%
DPoS (Delegated Proof of Stake)Total delegation >= 10,000 QOR35%
PoS (Proof of Stake)All remaining validators25%
Not active on the live networks

The pool classification, pool-weighted proposer selection and pool reward weights are implemented in the x/qca module and their parameters are on chain (qorechaind query qca config), but they are not yet wired into block production or reward distribution. Today block proposal rotates by stake in the standard way and rewards are shared in proportion to bonded stake, less each validator's commission. Which pool a validator "belongs" to does not change what you receive.


Bonding Curve Rewards​

QoreChain's design also defines a bonding-curve reward formula:

R = beta * S * (1 + alpha * log(1 + L)) * Q(r) * P(t)
VariableDescription
RReward amount for the period
betaBase reward rate (protocol parameter)
SStaked amount
alphaLoyalty coefficient (protocol parameter)
LStaking duration in epochs
Q(r)Quality multiplier derived from the validator's reputation score r
P(t)Pool multiplier at time t (40%, 35%, or 25% depending on pool)
Not active on the live networks

The bonding-curve calculation, like the pool classification above, is not called by the live chain: rewards are not computed with this formula, and neither staking duration nor validator reputation changes them today. The parameters (bonding_alpha, bonding_beta) exist on chain but have no effect.


Slashing and Jailing​

Slashing on QoreChain follows the standard Cosmos SDK slashing module with these live parameters (qorechaind query slashing params):

EventRuleConsequence
DowntimeSigning fewer than 5% of the last 10,000 blocks (about 8.7 hours at the mainnet's roughly 3.1-second blocks)Jailed for 600 seconds; 1% of stake slashed
Double-signingSigning two different blocks at the same height5% of stake slashed

Slashing applies to a validator's total bonded stake, so delegators bear their proportional share. It can also reach stake that is already unbonding from a slashed validator, which is why the unbonding period is a security measure and not only a waiting time.


Querying Validator Information​

Look up details about any validator:

qorechaind query staking validator <validator_operator_address>

Example:

qorechaind query staking validator qorvaloper1abc...xyz

List all active validators:

qorechaind query staking validators --status BOND_STATUS_BONDED

Query your current delegations:

qorechaind query staking delegations <delegator_address>

tip
  • Look at a validator's commission, uptime and track record before delegating; a validator's pool or reputation does not currently change the rewards you receive.
  • Redelegation takes effect immediately with no penalty and no lock. The limits are the 7-entry cap on simultaneous redelegations along the exact same route and the rule that freshly redelegated stake cannot be moved on from the destination validator until it matures.
  • The 21-day unbonding period is a security measure. During this time, slashing events can still affect your tokens.