Cosmos
Cosmos Hub staking and ATOM validator selection
Last updated
Cosmos Hub staking lets ATOM holders delegate to an active validator that participates in consensus and earns protocol rewards. Choosing an operator involves its signing record, commission terms, and share of voting power. Delegated tokens remain under the delegator's account authority, while validator faults can still trigger slashing. Review the operator before bonding, retain liquid ATOM for transaction fees, and account for the chain's unbonding rules when planning access to the balance.
The short version: A validator's commission applies to rewards, while its signing performance can affect both reward eligibility and the delegated principal.
Active validators and inactive candidates
An active validator participates in consensus and receives staking rewards; an inactive candidate can hold delegations without earning ongoing consensus rewards. Bonded status identifies membership in the active set. Selection depends on staking power and the network's configured validator limit, with jailed operators excluded. A registered validator name therefore does not establish that its delegations currently earn rewards. Among active operators, commission affects the reward allocation, while signing performance indicates whether the operator fulfills its consensus duties.
Active status can change after stake movements or jailing. The validator record identifies the operator address and commission settings; a display name alone cannot establish either.
How does validator commission affect ATOM rewards?
Validator commission reduces the rewards allocated to delegators, without deducting that percentage from the amount initially delegated. The distribution mechanism allocates rewards proportionally to stake after the applicable network deductions and validator commission.
Compare the current commission with the operator's maximum rate and maximum daily change. These settings constrain future increases, so today's rate does not describe the full commission policy. The daily change limit concerns movement in the commission fraction. It is distinct from the maximum rate that the operator can ultimately charge. Network rules can also impose a minimum commission.
Annual reward estimates depend on network issuance, total bonded stake, and validator participation. An operator cannot set those network inputs through its commission field.
Transaction fees sit outside this reward split. Delegating, withdrawing rewards, and changing a delegation involve transactions whose fees affect the account's spendable balance. A displayed reward estimate may already include commission; applying the deduction again would understate the expected allocation.
Does an ATOM validator take custody of delegated tokens?
Native delegation does not grant the validator spending authority over the delegator's account. Bonded ATOM moves into the chain's staking module, which records the delegator's share of the selected validator's stake. The account authorizes later staking transactions, and the balance remains subject to unbonding and slashing rules. Control of the account therefore coexists with limits on when bonded tokens become transferable.
A native delegation request identifies a validator and an amount. It does not require sending ATOM to the operator's personal account or disclosing a recovery phrase. A custodial staking service creates a different trust relationship because the service controls deposited tokens. Its withdrawal terms can differ from the native unbonding process.
Signing reliability and the distribution of stake
Validator faults can affect rewards and principal, so signing performance provides different information from commission terms. Missing too many required consensus signatures can trigger downtime penalties and jailing. Double signing involves conflicting votes at the same height, round, and voting stage. It can lead to slashing and permanent tombstoning of the validator's consensus key on this chain. The chain's slashing parameters determine the relevant thresholds and penalty fractions. Past participation records help identify outages, although they cannot establish how an operator will perform in the future. Incident explanations can clarify whether the problem involved connectivity, maintenance, or signing infrastructure.
Splitting stake limits exposure to an individual operator. Shared infrastructure or a network-wide fault can still affect several validators together.
Voting power measures consensus weight; it does not certify operator quality. Delegating across independently operated validators can spread that weight, including toward smaller operators that remain active. Review each candidate's signing history and commission terms when spreading delegations.
Confirming a first delegation
All amounts, rates, and assumed validator conditions in this example are hypothetical. The holder wants to delegate 38.8 ATOM to an active validator with an 8% commission, and will continue only after confirming the delegation on-chain. Before signing, the holder requires a matching operator record and enough spendable ATOM to cover the delegation plus the quoted transaction fee.
For a pre-commission reward share of 0.38 ATOM over an unspecified period, commission takes 0.38 × 0.08 = 0.0304 ATOM. The calculated remainder is 0.3496 ATOM before any withdrawal transaction fee. The assumed reward share already excludes network-level deductions and does not predict earnings from the 38.8 ATOM delegation. Changing the reward share changes both amounts; changing commission changes their split.
With those prerequisites satisfied, the holder signs and submits the native delegation. In the successful case, the transaction executes in a block and the corresponding delegation record identifies the holder and selected validator. The transaction's delegation amount matches 38.8 ATOM. A transaction hash alone cannot prove successful execution, so a pending or failed transaction does not satisfy the holder's condition for continuing.
When does delegated ATOM become spendable again?
ATOM undelegated from a bonded validator becomes spendable when the chain completes its unbonding entry. The entry records a completion time under the applicable staking parameters. Unbonding releases the requested portion; any remainder stays delegated. The unbonding portion stops earning staking rewards, and it can remain exposed to slashing for offences committed while bonded. A completion timestamp describes the scheduled release, while the account balance reflects whether the chain has processed it.
Undelegation starts a new unbonding period even when the validator is already unbonding or unbonded. The chain calculates the entry's completion time from the undelegation block time and the current unbonding parameter.
A successfully executed redelegation changes the recorded operator without first returning tokens to the spendable balance. During an unfinished redelegation, moved stake can still be slashed for an offence that the source validator committed before the move. Moving to a bonded destination allows that stake to participate through the new operator.
An unfinished inbound redelegation prevents the same delegator from redelegating out of the receiving validator. The chain also caps pending redelegation entries for each delegator and source-and-destination validator pair. Reaching that cap blocks another redelegation for the same pair until an entry clears. These restrictions do not freeze every staking action across the account.
Reviewing the operator after bonding
An uptime percentage needs its observation window to have a useful basis. A long reporting period can obscure recent problems, so recent missed signatures deserve their own examination. Operator incident reports add context about outages and planned remediation, while the on-chain signing record shows participation. Commission updates also need attention because the terms that applied when bonding can subsequently change within their permitted limits.
Keeping freely spendable ATOM liquid preserves transfer access. Delegated ATOM can earn rewards through an active validator, while the balance remains exposed to validator faults and unbonding rules.
Cosmos: reader questions
Do ATOM staking rewards compound automatically?
Native staking rewards do not automatically increase the bonded delegation. They need to be withdrawn and delegated again to become additional stake. An automatic reinvestment feature belongs to the particular service and its authorization model. Fees paid from the same account reduce its available balance, which matters when comparing compounded estimates with ordinary staking rewards.
Why did my claimable rewards drop after adding ATOM to an existing delegation?
Updating an existing delegation settles its accrued rewards through the distribution module. The claimable figure can reset after that settlement, with the payout reflected at the configured reward withdrawal address. Transaction events help distinguish this payout from a display issue or a reduction caused by slashing.
Will a validator with more self-delegated ATOM pay me extra rewards?
A validator's self-delegated ATOM does not create a bonus multiplier for other delegators. The operator's own delegation shares exposure to slashing, which helps explain its financial incentives. A large self-delegation does not establish reliability; commission and active status still govern relevant parts of the reward comparison.
Can I delegate a fraction of an ATOM?
Native ATOM delegations can include fractional tokens. The chain represents amounts in uatom, with 1 000 000 uatom equal to one ATOM. The submitted amount must resolve to a whole number of uatom. A wallet's entry format or a service's minimum can impose additional restrictions.
Does cancelling an ATOM unbonding request restore the original delegation?
Cancelling an eligible unbonding entry re-delegates the specified amount to its original validator. The amount cannot exceed the entry's remaining balance, and the entry must not have matured. The validator must remain eligible, including not being jailed. Cancellation does not select a different operator, and an interface must support the cancellation transaction.
Do I need to keep my wallet open to earn ATOM staking rewards?
Your wallet can remain closed because the delegation exists in chain state and the validator operates the node. Closing the application does not end an accepted delegation. Rewards continue under the chain's distribution rules while the validator remains eligible to earn them; account access is needed to authorize later transactions.
What ATOM staking details can other people see on-chain?
Public chain records expose the delegator address, selected validator, and associated stake. Reward withdrawals and undelegation transactions also leave public records. These records do not identify a person's real name by themselves, although connecting an address to an identity can make that person's staking activity attributable.