Root Staker
A root staker is a TAO holder who stakes on the Root Subnet through validators. Root Subnet, also called Subnet Zero, is the subnet-agnostic staking venue in Bittensor (Glossary: Root Staker, Glossary: Root Subnet/Subnet Zero).
The term names the holder role in Root Subnet staking. It should not be confused with a validator role, an alpha staker role, or a root-claim preference.
In plain language, root staker answers who is supplying TAO through the Root Subnet path. It does not answer which validator should be selected or how later dividends are handled. The core reading is holder, Root Subnet, and validator.
Root Subnet Staking
Root Subnet staking lets TAO holders stake through validators in a subnet-agnostic setting. That is different from subnet-local alpha staking, where staking belongs to a particular subnet’s alpha-token context (Staking and delegation overview, Emission: Distribution).
This asset and venue distinction is the center of the term. A root staker supplies TAO through Root, while alpha-side staking belongs to a specific subnet’s alpha context.
That distinction keeps Root Subnet staking separate from alpha-side participation in a specific subnet. Dividend references can mention the role because Root Subnet staking can feed dividend outcomes.
Delegation Context
A root staker participates by delegating TAO to a validator on the Root Subnet. Staking and delegation vocabulary keeps the holder and validator roles separate: the holder supplies stake support, while the validator receives that support (Staking and delegation overview, Glossary: Root Staker).
Root staker is therefore descriptive rather than advisory. It names the TAO holder in the Root Subnet staking relationship without choosing a validator or explaining every staking action.
Most references only need this division: root staker provides stake, and validator language names the receiver of delegated support.
Dividends and Root Claims
Root-routed stake can earn alpha dividends from subnets. Root claims explain how those accumulated dividends are handled, including Keep and Swap outcomes (Root Claim Overview, Emission: Distribution).
That claim layer comes after the staking role. Root staker names the holder side of the position; root claims describe how accumulated dividends from that position can later be handled.
This is the concise difference from root claim type: root staker identifies the holder-side staking relationship, while root claim type identifies the Keep or Swap handling setting for processed dividends.
Related Measures
Root proportion is nearby vocabulary because it describes how root-routed TAO appears in a subnet’s dividend context. Root staker is the role term, while root proportion is the subnet-level measure (Glossary: Root Proportion, Glossary: Root Staker).
Keeping those terms separate helps prevent a holder role from being read as a subnet metric, validator recommendation, or dividend outcome.
A root-proportion statement can describe a subnet’s dividend split. A root-staker statement instead identifies the holder role connected to TAO routed through Root.
Development Stage Context
Bittensor separates localnet, testnet, and mainnet environments. Root-staker examples from one environment should not be treated as evidence for another because validators, balances, dividends, and root staking state are environment-specific (Bittensor Networks, Introduction to Bittensor: Subnet development).
Localnet examples can test root staking mechanics in isolation. Testnet examples add shared non-production staking state. Mainnet root-staker interpretation concerns production Root Subnet relationships on the active network.
Relationship to Yuma Consensus
Root Staker 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, root staker 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
Root staker identifies a TAO holder staking through validators on the Root Subnet (Glossary: Root Staker, Glossary: Root Subnet/Subnet Zero).
Validator language names the receiver of delegated support. Root claim language names dividend handling. Root staker is the holder-side staking term.
Root Staking Uses Subnet Zero, Not Alpha Subnets
The Glossary: Root Subnet/Subnet Zero describes the root subnet as the only subnet without its own alpha currency. Root staker vocabulary therefore names TAO staking on Subnet Zero rather than alpha-denominated stake on an alpha subnet (Understanding Subnets).
When the focus is subnet alpha held through staking, alpha staker is the more precise term.
Root Claims Handle Dividend Outcomes for Root Stakers
Root Claim Overview documentation describes how root stakers can manage dividend-related outcomes from root-subnet staking. Root staker names the holder role; root claim vocabulary names the dividend-handling path (Emission: Distribution).