Subnet Miner
A subnet miner is the task-performing role inside a Bittensor subnet. Miners perform the work that subnet validators evaluate (Glossary: Subnet Miner, Understanding Subnets).
The term belongs to subnet incentive vocabulary. It names the work-producing role in the subnet flow; validator, scoring, consensus, and emission language describe later parts of that flow.
In plain language, subnet miner answers: who is doing the work that validators score in this subnet? A miner produces the output; a validator evaluates it; consensus aggregates those evaluations into miner incentives. The miner role is the entry point in that sequence (Glossary: Subnet Miner).
For a reader, the distinction from subnet validator matters most when reading evaluation results. A miner produces; a validator evaluates. Their roles are complementary and subnet-specific, so a miner from one subnet does not automatically perform in another subnet (Understanding Subnets).
Work Role
The miner role is tied to the subnet’s work target. A miner in one subnet may produce a different kind of output than a miner in another subnet because each subnet can define its own goals and standards (Understanding Subnets, Glossary: Subnet Task).
This keeps miner vocabulary scoped to the subnet being discussed. The role is defined by the work a subnet asks miners to perform.
That scope is the main reason the word miner is not interchangeable across subnet examples. A general miner claim still needs the subnet task or mechanism that gives the work its meaning.
Work Product Versus Incentive Outcome
The subnet miner supplies work that validators later evaluate under the subnet’s rules. The incentive mechanism then connects task, protocol, and evaluation method into a scoring path (Understanding Incentive Mechanisms, Glossary: Subnet Miner).
For readers, miner names who produces requested work. It does not by itself define emissions, weights, or final incentive outcomes.
The incentive path depends on more than the work product. Returned work can be scored, converted into validator signals, aggregated through consensus, and connected to emissions by the subnet’s mechanism design.
Relationship to Validators
Subnet miners and subnet validators form the core work-and-evaluation relationship inside a subnet. Miners provide work, and validators measure that work against the subnet’s standards (Glossary: Subnet Miner, Glossary: Subnet Validator).
The distinction is role-based. Subnet miner names the producing side; subnet validator names the evaluating side, including measurement, weights, and consensus signals.
Relationship to Subnet Task
A subnet miner is the role performing the work, while the subnet task is the work target itself. The glossary connects subnet tasks to the work miners perform, and the incentive-mechanism documentation places task design inside the broader subnet mechanism (Glossary: Subnet Task, Understanding Incentive Mechanisms).
Keeping those terms separate makes the article easier to read: the miner is the role, and the task describes what that role is expected to produce.
Task language is especially important for comparisons. Two miner examples can both be valid Bittensor examples while still describing different work because their subnet tasks differ.
Mechanism Scope
Some subnets can run multiple incentive mechanisms in parallel. In that case, miner work and validator evaluation belong to the mechanism being discussed (Multiple Incentive Mechanisms Within Subnets, Glossary: Multiple Incentive Mechanisms).
This prevents a result in one mechanism from being treated as a complete statement about miner work across every mechanism in the subnet.
Mechanism scope also keeps emissions language precise. A miner result from one mechanism does not automatically describe every work path, evaluation path, or incentive path inside the same subnet.
Development Stage Context
Bittensor separates localnet, testnet, and mainnet environments. Miner examples from one environment are not evidence for production subnet performance in another environment (Bittensor Networks, Introduction to Bittensor: Subnet development).
Localnet can demonstrate miner role mechanics in isolation. Testnet belongs to shared non-production state. Mainnet belongs to production chain history.
Concrete miner claims need the subnet, mechanism, network, and source that produced the example.
Relationship to Yuma Consensus
Subnet Miner 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, subnet miner 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
Subnet miner names the work-producing role inside a subnet. It describes the work side of subnet incentives rather than how-to steps, performance reports, account labels, or claims about a specific miner’s output (Glossary: Subnet Miner, Understanding Subnets).
A specific miner’s rank or incentive is a consensus-and-network outcome to read from live subnet data, not something the term itself reports (Glossary: Subnet Miner).
Registration Grants a UID Before Mining Work
Official Mining: Miner registration documentation describes registering with a subnet to receive a UID before a miner can take part in mining work. Register vocabulary names that subnet-entry step; subnet miner names the work-producing role that follows once entry succeeds (Glossary: UID Slot).
Miner reading therefore starts after registration. The role produces subnet task output; registration places the hotkey into the participant set validators can evaluate.
Validators Score Miner Output Through Weight Vectors
Yuma Consensus describes validators periodically submitting vectors that rank miner work they have evaluated. Those validator weights are the evaluation signals subnet miners receive after producing output under the subnet task (Understanding Incentive Mechanisms).
Subnet miner names who produces work; validator weights name how that work is scored before consensus merges many validator signals.
Miner Incentives Follow Rank After Consensus
Yuma Consensus: Miner emissions documentation divides miner-side subnet emissions by aggregate rank after validator weights are clipped and combined. Miner incentives therefore sit downstream of both evaluation and consensus processing (Glossary: Incentives).
That keeps miner role vocabulary separate from payout vocabulary. Producing useful subnet work is the input; rank and incentives describe the emission outcome after consensus runs.