Root Claims
Root claims handle alpha dividends earned through Root Subnet staking. They decide whether earned alpha remains as subnet alpha or is converted into TAO and restaked on Root (Root Claims, Understanding Subnets).
The mechanism is narrow. It is about dividend treatment after rewards accrue, not about moving the original root stake or explaining a general staking procedure.
Root Subnet Context
The Root Subnet, also called Subnet Zero, is the special subnet where validators can register and TAO holders can stake in a subnet-agnostic way. Root claims exist because stake placed through that Root Subnet path can receive alpha dividends from other subnets while the underlying stake remains associated with the Root Subnet (Glossary: Root Subnet/Subnet Zero, Root Claims).
That separation gives root claims their role. The original stake remains tied to Root Subnet, while earned alpha needs a handling rule once it is claimable.
Keep and Swap Outcomes
Root claims have two outcomes. Keep leaves earned alpha as the alpha of the subnet that produced it. Swap converts the earned alpha into TAO and restakes that dividend output on Root (Root Claims, Emission).
Both outcomes apply to dividends, not to the original root stake. This keeps root claims separate from unstaking, moving stake, or changing delegation.
That distinction is important when reading root-staking material: a claim changes the treatment of earned dividend output, while the root stake remains the staking position that produced access to those dividends.
Claim Type Context
Root claim type is the preference that determines which outcome a root claim uses. Keep and Swap are routing choices for dividend output, while a root claim is the handling of accumulated dividends (Root Claims, Glossary: Root Staker).
The important concept is the dividend outcome: Keep preserves alpha exposure from the producing subnet, while Swap routes the dividend into TAO on Root.
Claim Processing
Root claims can be processed automatically by the chain or manually through the root-claim extrinsic path. In both cases, the configured Keep or Swap preference is what determines how the claim treats accumulated alpha dividends (Root Claims).
This keeps the processing method separate from the outcome choice. Automatic and manual claims describe how a claim is triggered, while Keep and Swap describe what happens to the dividend output.
Emission Scope
Root-claim swaps sit inside Bittensor emission accounting. They handle dividend output, while flow-based emissions track subnet inflows and outflows for emission distribution (Root Claims, Emission).
This keeps root claims narrower than emissions overall. Root claims explain what happens to dividends from Root Subnet staking after they accrue; they do not describe every reward distribution mechanism in Bittensor.
Development Stage Context
The Introduction to Bittensor describes subnet development as moving from localnet to testnet and then mainnet. For root claims, that sequence changes how readers should interpret alpha-dividend handling and Root Subnet staking examples.
In localnet, root-claim examples can be exercised in an isolated environment. Local claim settings and dividend outcomes reflect local chain configuration rather than production Root Subnet state.
On testnet, root claims can be observed in a shared, non-production network. Testnet Root Subnet dividend context is separate from mainnet staking and claim history (Root Claim Overview).
On mainnet, root claims describe live dividend-handling choices for Root Subnet staking on the production Bittensor network (Glossary: Root Subnet/Subnet Zero).
The Bittensor Networks reference separates mainnet, testnet, and localnet. A root-claim example from one environment should not be read as representing production dividend outcomes in another environment.
Relationship to Yuma Consensus
Root Claims 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 claims 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 claims should be read as dividend-handling vocabulary for Root Subnet staking. The claim type sets how accumulated alpha dividends are handled after they are claimable; it does not rename the original root stake, guarantee future dividend amounts, or describe a general unstaking action (Root Claims, Glossary: Root Staker).
Original Root Stake Stays Staked in Both Modes
Official Root Claims documentation states that the initial TAO staked to a validator on the Root Subnet remains staked on root in both Keep and Swap modes. Only the alpha dividends earned from other subnets are routed differently.
Root claims vocabulary therefore applies to dividend handling, not to moving the underlying root stake position that produced those dividends.
Swap Claims Do Not Count as Subnet TAO Outflows
The same root-claims reference notes that Swap-mode conversions do not count as TAO outflows for flow-based emission calculations on the subnet that produced the alpha. Claiming and converting alpha dividends to TAO therefore does not, by itself, reduce that subnet’s net-flow allocation signal.
Keep mode instead accumulates alpha on the producing subnet, while Swap mode restakes the converted TAO on root. The emission exception applies to the Swap path’s accounting rather than to every root-staker action.
Automatic Claims Use a Minimum Dividend Threshold
Root-claims documentation describes automatic processing only when accumulated alpha dividends
exceed a minimum threshold, documented as 500,000 RAO (0.0005 TAO equivalent). Manual claims can be
triggered through the claim_root extrinsic, specifying up to five subnets per call.
That split keeps threshold and timing separate from the Keep-or-Swap preference. Both automatic and manual paths apply the configured claim type once dividends are processed (Root Claims).