Nominate
To nominate is to stake TAO with a validator or delegate in Bittensor. The official Nominate glossary describes nomination as the staking process by which TAO holders participate through validators.
Delegation Context
Nominate is the action side of the nominator relationship. A nominator is the account role, while nomination names the act of staking TAO with the validating side of a delegation relationship.
Staking Context
The official staking and delegation documentation uses delegation to describe staking TAO with validators. In Taopedia prose, nominate should be read as delegation vocabulary rather than as a subnet role, account count, or chain-state claim.
Validator Hotkey Context
The Glossary: Nominate describes nomination as staking TAO on a validator’s hotkey so token holders can participate in subnet emissions through active validators. The term names the delegation action and its validator-side target in staking vocabulary, distinct from the nominator account role.
References: Glossary: Nominate, Glossary: Nominator
Nomination Names a Delegation Action, Not a Role
Nominate should not be read as a nominator account label, a validator permit, or proof that emissions were received. The term names the staking action of attaching TAO to a validator hotkey (Glossary: Nominate, Glossary: Nominator).
The nominator role names who supplies delegated stake; nominate names the delegation act itself.
Staking Documentation Covers Procedures, Not This Label
This article is a concept boundary. It does not provide staking procedures, CLI commands, or live chain data. Official staking and delegation documentation covers how nomination is submitted on chain (Staking and delegation documentation).
Readers should keep procedural claims tied to those references rather than to nominate vocabulary alone.
Nomination Applies Within a Subnet Context
A netuid identifies which subnet is in scope, while nominate names the delegation action that supports a validator participating in that context (Glossary: Netuid, Glossary: Nominate).
A precise claim should name both the subnet context and the validator hotkey receiving delegated support.
Nomination Is a Chosen Staking Action
Nomination names a deliberate delegation act by a TAO holder. The Glossary: Nominator describes a nominator as an account that stakes TAO with validators, while nominate names the act of making that delegation choice.
That keeps the action separate from automatic routing mechanisms. A holder chooses nomination; it is not the same vocabulary as autostaking or miner emission routing.
The Glossary: Nominate also ties nomination to staking TAO on a validator hotkey so token holders can participate through active validators.
References: Glossary: Nominate, Glossary: Nominator
Nomination Versus Unstaking
Nomination adds or adjusts delegated support for a validator. Unstaking removes stake from the delegation model. The Glossary: Unstake describes unstaking as withdrawing delegated stake.
Using the right verb keeps staking prose precise. Nominate is not a synonym for unstake or transfer.
Unstaking ends or reduces delegated exposure, while nomination establishes or changes which validator hotkey receives that delegated support.
References: Glossary: Nominate, Glossary: Unstake
Nomination Versus Moving Stake
Moving stake rearranges an existing delegated position between hotkeys or subnets without treating the action as a fresh nomination from scratch. The Staking and delegation overview lists moving stake alongside other stake-management operations separate from the initial delegation choice.
Nominate therefore belongs with first-time or adjusted delegation support, while moving stake belongs with rearranging where an existing staked position already sits.
Both verbs concern stake management, but they name different kinds of delegation changes.
References: Staking and delegation overview, Glossary: Nominate
Relationship to Multiple Mechanisms
Nomination attaches TAO support to a validator inside a subnet. The Glossary notes that each subnet has one or more incentive mechanisms.
For readers, nominate still names the delegation action in staking vocabulary. That action supports a validator position in one subnet, which may run more than one incentive mechanism.
References: Multiple Incentive Mechanisms Within Subnets, Glossary: Incentive Mechanism
Relationship to Autostaking
Nominate and autostaking both result in staked TAO on a validator, but they describe different things. To nominate is the act of staking TAO with a validator or delegate, as the Glossary: Nominate describes — a staking action a TAO holder chooses to take. Autostaking, by the Autostaking documentation, is a mechanism that automatically routes a miner’s emission proceeds into a staking position on a chosen validator.
For readers, nominate names a deliberate staking action by a token holder, while autostaking names an automatic routing of a miner’s emissions into stake. The two are not interchangeable: nomination is a chosen act of staking existing TAO with a validator, whereas autostaking continuously converts newly earned emissions into stake on a chosen validator without a separate action each time. Both place stake on a validator, but one is a staking action a holder takes and the other is an ongoing automatic mechanism.
References: Glossary: Nominate, Autostaking
Relationship to Subtensor
Nominate and Subtensor are related but different parts of Bittensor chain vocabulary. Subtensor names Bittensor’s layer 1 blockchain and system of record, while nominate names the staking action of attaching TAO to a validator hotkey recorded through chain-layer delegation state. The Glossary: Subtensor describes the blockchain layer, and the Glossary: Nominate describes nomination as staking TAO on a validator hotkey.
For readers, Subtensor names the chain layer, while nominate names the delegation action recorded on that layer.
References: Glossary: Subtensor, Glossary: Nominate
Relationship to Netuid
Nominate and a netuid are related but different parts of Bittensor vocabulary. A netuid identifies a subnet on the network, while nominate names the action of staking TAO with a validator participating in that subnet context. The Glossary: Netuid places netuid at the subnet level, and the Glossary: Nominate describes nomination as staking TAO on a validator hotkey.
For readers, a netuid selects which subnet context is in scope, while nominate names the delegation action that supports a validator in that context.
References: Glossary: Netuid, Glossary: Nominate
Relationship to Nominator
Nominate and nominator are related but different scopes in Bittensor staking vocabulary. Nominator names the TAO-holder account role that supplies delegated stake, while nominate names the staking action that attaches TAO to a validator hotkey. The Glossary: Nominator describes a nominator as an account that stakes TAO on a validator hotkey, and the Glossary: Nominate describes nomination as staking TAO on a validator hotkey.
For readers, nominator names the account role, while nominate names the delegation action carried out by that role.
References: Glossary: Nominator, Glossary: Nominate
Relationship to Delegate
Nominate and delegate are related but different sides of Bittensor delegation vocabulary. Nominate names the action of staking TAO with a validator hotkey, while delegate names the subnet validator role that receives that staked TAO and performs validation work. The Glossary: Nominate describes nomination as staking TAO on a validator hotkey, and the Glossary: Delegate defines a delegate as a subnet validator that receives staked TAO from delegators.
For readers, nominate names the supplying action, while delegate names the receiving validator role on the other side of that relationship.
References: Glossary: Nominate, Glossary: Delegate
Relationship to Coinbase
Nominate and coinbase are related but different parts of how delegated stake influences emissions. Nominate is the staking action that attaches a TAO holder’s stake to a validator hotkey. Coinbase is the per-block protocol mechanism that drives TAO emission, injects TAO into emitting subnets’ pool reserves, accumulates pending emissions, and checks epoch boundaries to trigger Yuma Consensus rounds. The Glossary: Nominate describes the staking action, and the Coinbase Implementation documentation describes the per-block emission operation.
Nominating increases a validator’s effective stake, which Yuma Consensus uses to weight that validator’s influence during coinbase-triggered epoch rounds. Coinbase then distributes validator dividends from each epoch’s emissions, and a share of those dividends flows back to nominators in proportion to the stake they delegated. Nominate is the action that positions stake behind a validator; coinbase is the mechanism that converts that validator’s consensus participation into the emissions a nominator can ultimately share in.
Development Stage Context
The Introduction to Bittensor describes subnet development as moving from localnet to testnet and then mainnet. For nominate, that sequence changes how readers should interpret evidence about TAO delegation and validator stake relationships.
In localnet, nomination can be tested in an isolated environment. Stake delegated to validators in localnet reflects local chain configuration and does not represent production validator associations or real TAO.
On testnet, nomination can be observed in a shared, non-production network. Testnet nomination affects testnet validator stake but remains separate from mainnet delegation state and real nominator relationships.
On mainnet, nominating is a live Subtensor staking action that changes real TAO positions and validator stake on the production network. The Staking and delegation documentation describes the delegation mechanics that apply on mainnet.
The Bittensor Networks reference separates mainnet, testnet, and localnet. A nomination example from one environment should not be read as representing validator stake or delegation associations in another environment.
Relationship to Yuma Consensus
Nominate and Yuma Consensus describe related parts of Bittensor’s incentive system. Yuma Consensus is the on-chain process that aggregates validator weight signals within a subnet into miner incentives and validator dividends, applying consensus clipping, bonding, and emission calculation (Yuma Consensus).
For readers, nominate names a specific part of that incentive picture, while Yuma Consensus names the consensus process that turns validator weights into the resulting incentives and dividends.
Reader Boundary
Nominate should not be read as a subnet role, a completed governance appointment, or proof that emissions were received. In staking vocabulary it names the delegation action of attaching TAO to a validator hotkey (Glossary: Nominate, Staking and delegation documentation).
Nomination Targets a Validator Hotkey
The nominate glossary entry describes staking TAO on a validator hotkey so token holders can participate through active validators. That keeps the action tied to a validator-side target rather than to a generic account label (Glossary: Nominate, Glossary: Delegate).
For readers, nomination prose should name the validator hotkey or delegation context being supported.
Nomination Differs From Unstaking and Moving Stake
Unstaking withdraws delegated stake, while moving stake rearranges an existing position between hotkeys or subnets. Nominate belongs with establishing or adjusting delegation support rather than with those other stake-management verbs (Glossary: Nominate, Glossary: Unstake, Staking and delegation overview).
Using the right verb keeps staking claims precise about which delegation change is being described.
Governance Role Scope
Nominate language should keep the governance role being nominated visible. Governance sources separate proposal flow, Senate participation, and role-specific authority, so nomination claims should identify the body or process they affect (Governance Overview, Senate).
This scope prevents a nomination from sounding like completed governance approval. A nomination can be part of selecting or authorizing a role, while voting, approval, closure, and execution remain separate steps.