Delegate
A delegate is a subnet validator that receives staked TAO from delegators and performs validation tasks in one or more subnets (Glossary: Delegate, Glossary: Subnet Validator).
The term sits where Bittensor’s validation role and delegated-stake vocabulary meet. It should not be confused with the nominator role that supplies TAO support.
Validation and Staking Role
Delegate is a role term for the receiving side of a staking relationship. The delegate receives staked TAO and performs validation work for subnet consensus (Glossary: Delegate, Staking and delegation overview).
This makes delegate more specific than a generic staking reference. It names a validator role that can receive staked TAO from others while carrying out validation tasks.
Nominator Boundary
A delegate is paired with the accounts that supply stake. A nominator is the TAO-holder role that stakes with validators, while delegate names the validator that receives that stake (Glossary: Nominator, Glossary: Delegate).
The relationship is directional: nominators supply delegated stake, and delegates receive that stake while performing validation work. Keeping the two sides separate prevents delegate from being read as the account role that supplies TAO.
Delegate Stake and Effective Stake
Delegate stake and effective stake refine the staking side of the delegate role. Delegate stake is the TAO the delegate stakes themselves. Effective stake is the broader total associated with the delegate, including the delegate’s own TAO and TAO delegated by nominators (Glossary: Delegate Stake, Glossary: Effective Stake).
These terms keep the role and stake amounts separate. Delegate names the receiving validator role; delegate stake names the self-staked component; effective stake names the combined total behind that role.
Delegated Stake Boundary
Delegated stake supports the delegate’s validator role; it does not turn the nominator into the validator for that subnet. The delegation overview describes nominators staking to validators, while the delegate glossary entry keeps delegate attached to the receiving validator role (Staking and delegation overview, Glossary: Delegate).
That boundary keeps stake support separate from role assignment. A nominator can add stake behind a delegate, but delegate still names the validation side of the relationship.
Permit Context
Validation rights are separate from the role label. A validator permit is the permission flag for validation rights in a subnet (Glossary: Validator Permit, Glossary: Delegate).
That boundary keeps delegate from carrying every permission detail by itself. Delegate names the staking-and-validation role; permit vocabulary describes validation rights for the relevant subnet context.
Development Stage Context
The Introduction to Bittensor describes subnet development as moving from localnet to testnet and then mainnet. Delegate examples need that context because validator sets, staking totals, and dividend outcomes belong to the network where they were observed (Bittensor Networks).
Localnet delegate examples can test role wiring in isolation. Testnet examples add shared non-production delegation state. Mainnet delegate interpretation concerns production validator relationships on the active network.
Delegate examples from one environment should not be treated as evidence for another.
Relationship to Yuma Consensus
Delegate 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, delegate 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
Delegate names the receiving validator role in a staking relationship. It is not the nominator role that supplies TAO support, nor a balance report or dividend quote (Glossary: Delegate, Glossary: Nominator).
Autostaking and Emission Context
Delegates are a destination for miner autostaking. When a miner uses autostaking, mining emissions are automatically routed as stake to the configured delegate rather than requiring a separate staking transaction. The delegate, as the receiving validator, earns dividend outcomes as staked TAO accumulates behind its hotkey (Auto Staking for Miners, Emission).
This connection puts delegate in the miner-reward path. A miner’s autostaking configuration determines which delegate receives the emission-derived stake, which keeps delegate selection from being purely a validator-side decision.
Yuma Consensus shapes how delegate validators receive reward outcomes. Validator dividends depend on how the consensus process aggregates weight signals, and delegates serve as the recipient side of those dividend outcomes (Yuma Consensus, Emission).
For readers, delegate belongs at the intersection of validation work, received staked TAO, and dividend outcomes. Autostaking explains one source of incoming stake; Yuma Consensus explains how validation work translates into the dividend outcomes that make that stake worth holding behind the delegate hotkey (Auto Staking for Miners, Yuma Consensus).
Effective Stake Combines Self-Stake and Nomination
The Glossary: Effective Stake describes the total staked TAO associated with a delegate after both the delegate’s own stake and nominator support are counted. Delegate stake names only the self-supplied portion; effective stake names the broader backing total.
That distinction keeps role and amount separate. Delegate vocabulary names the receiving validator; effective stake names how much TAO sits behind that validator after nomination is included.
Validator Take Splits Delegated Emission Returns
Emission: Distribution documentation places validator take in the distribution stage that follows consensus. The validator keeps its configured share from emissions tied to delegated stake before the remainder flows to nominators (Staking and delegation overview).
Delegate vocabulary names the receiving validator role; take vocabulary explains why delegated support does not automatically return the full validator-side emission total to nominators.
Stake Weight Scales the Delegate’s Consensus Influence
Understanding Subnets: Validator stake weight documentation describes stake weight as the influence measure used when Yuma Consensus merges validator signals. Delegated and self-staked support both feed that measure behind a delegate’s hotkey (Glossary: Stake Weight).
Stake therefore affects both backing totals and consensus influence. Effective stake names how much TAO is attached; stake weight names how strongly that delegate’s submitted evaluations count inside aggregation (Yuma Consensus).