Delegation Rewards
Delegation rewards are what a delegator earns for staking TAO to a validator instead of validating itself. By backing a validator with stake, a delegator shares in the rewards that validator produces, in proportion to how much stake it contributed. The documentation frames delegation as exactly this arrangement: stake placed with a delegate to share in the returns.
References: Staking and Delegation Overview
A Share of the Validator’s Earnings
A validator generates rewards from its role, and those rewards are split among the validator and the stake delegated to it. A delegator’s reward is its proportional slice of that flow, scaled by how much stake it added relative to everything else delegated to the same validator. More stake behind a validator means a larger share of the same pool, not a separate reward created from nothing.
References: Staking and Delegation Overview, Dividends
The Validator’s Take Comes First
Before delegators are paid, the validator keeps a take, a commission on the rewards. A delegator earns the remainder after that take is removed, so the take a validator sets feeds directly into delegator returns: a higher take leaves a smaller share for those who delegated. Comparing takes is therefore part of comparing what different validators offer a delegator.
References: Glossary: Validator Take
Why Delegate at All
Delegation lets a TAO holder earn from validation without operating a validator. The holder lends the weight of its stake to a validator it trusts and shares in the upside, treating the validator’s take as the cost of that convenience. The reward is the return on that choice, set against the effort and risk the delegator avoids by not validating directly.
References: Staking and Delegation Overview
The Other Side of Dividends
Delegation rewards and validator dividends describe one flow from two angles. Dividends name the validator-side result, while delegation rewards are the delegator’s share of that result after the take. Reading them together explains where a delegator’s earnings actually come from rather than treating them as a payment that appears on its own.
References: Dividends
Development Stage Context
The Introduction to Bittensor describes subnet development as moving from localnet to testnet and then mainnet. For delegation rewards, that sequence changes how readers should interpret validator take, stake placement, and reward-share examples.
In localnet, delegation reward flows can be tested in an isolated environment. Localnet tempo boundaries and delegator share examples do not represent production staking returns.
On testnet, delegation and reward distribution can be exercised in a shared non-production network. Testnet validator performance and delegator shares are separate from mainnet subnet state.
On mainnet, delegation rewards are live outcomes tied to production validators and delegators on subnets such as netuid 1. Observed returns depend on validator performance, take settings, and the stake distribution on the selected subnet (Staking and Delegation Overview).
The Bittensor Networks reference separates mainnet, testnet, and localnet. A delegation-reward example from one environment should not be read as representing production returns in another environment.
Relationship to Yuma Consensus
Delegation Rewards 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, delegation rewards 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
This page defines the concept at a high level and is not financial advice. What a delegator actually earns depends on the validator’s performance, the take it sets, and the live distribution of stake, all of which change over time. The durable point is the shape of the reward: a proportional share of a validator’s rewards, net of its take.
References: Staking and Delegation Overview
Delegator Shares Are Credited at Tempo End
Official Emission documentation describes subnet alpha as being distributed at the end of each tempo, after Yuma Consensus aggregates validator evaluations. A delegator’s reward is a proportional slice of the validator-side flow that results from that distribution stage, not a separate payout label on every block.
That timing keeps delegation rewards tied to finalized consensus outcomes. Validators and their delegators participate across the tempo, but the documented reward split — including the delegator share after validator take — applies when distribution runs at the tempo boundary on a subnet such as netuid 1 (Understanding Incentive Mechanisms).
References: Emission, Glossary: Tempo
Delegation Rewards Are Subnet-Local
Official Staking and Delegation Overview documentation treats staking as local to a subnet. TAO delegated to a validator on a subnet such as netuid 1 supports that validator inside that subnet’s emission context, separate from delegation sent to the same validator’s hotkeys on other netuids (Glossary: Netuid).
Delegation rewards follow the same locality. A delegator’s return depends on the validator relationship on the subnet where the stake was placed, rather than on a single network-wide reward pool copied across every subnet. Reading rewards subnet by subnet matches how delegated support is recorded in official staking material (Glossary: Delegation).
References: Staking and Delegation Overview, Glossary: Netuid
Alpha Subnets Record Delegated Stake in Alpha Units
Official staking documentation states that, except on the root subnet, stake held behind a validator hotkey is recorded in that subnet’s alpha units after TAO enters the subnet pool. On a subnet such as netuid 1, a delegator therefore commits TAO through the pool and holds subnet-denominated stake while earning from that validator relationship (Understanding Subnets).
That recording rule sits beside reward vocabulary rather than replacing it. Delegation rewards still name the delegator’s share of validator-side returns, while alpha-subnet staking explains the unit in which the supporting stake is tracked after the TAO-to-alpha conversion step (Understanding Slippage).
References: Staking and Delegation Overview, Understanding Subnets