Active UID
An active UID is a subnet participant slot that currently counts as usable for Bittensor subnet participation. The Bittensor glossary defines an active UID as a subnet UID that allows the associated participant to take part as a subnet validator or subnet miner (Glossary: Active UID).
The term matters because it is narrower than registration alone. Registration can place a participant in a UID slot, but active status describes whether that slot is currently treated as participating in the subnet context being observed (Glossary: UID Slot).
Subnet Role Context
Active UID language belongs to subnet participation. Bittensor documentation describes miners as the participants that produce subnet work and validators as the participants that evaluate miner responses, so active UID status is best read as a slot-level participation signal for those subnet roles (Miners, Validators).
That makes the word “active” a role-context label rather than a general account label. It does not say that every account action is active, or that every participant permission is present. It says the UID slot is currently usable for the subnet participant role being discussed.
Metagraph Activity Signal
The subnet metagraph is the main reference context for active status. Bittensor’s metagraph
documentation describes a subnet snapshot that includes participant fields, including an active
field tied to subnet state (Subnet Metagraph).
The activity window is also connected to subnet hyperparameters. The subnet-hyperparameter reference
defines activity_cutoff as a block-based setting used for activity timing, which is why active UID
claims should keep the relevant subnet and block context attached
(Subnet Hyperparameters).
Slot Assignment Versus Activity
A UID slot and an active UID answer different questions. The UID slot identifies the participant’s position inside a subnet, while active status says whether that position currently satisfies the activity condition being read from subnet state (Glossary: UID Slot, Glossary: Active UID).
This distinction keeps registration language from being overread. A participant can have a subnet slot while later activity evidence changes with block progression, metagraph state, or subnet activity windows. The active flag is therefore current state evidence, not a permanent label for the participant.
Netuid and Network Context
Active UID claims are scoped to a selected subnet. The glossary defines a netuid as the subnet identifier, and metagraph documentation reads subnet state through that selected context (Glossary: Netuid, Subnet Metagraph).
Network context also matters. Bittensor documentation separates mainnet, testnet, and localnet, so an active UID observed in one environment should not be treated as proof of the same participant state in another environment (Bittensor Networks).
For readers, a complete active-UID claim should preserve the subnet selection, network environment, and timing context. The same UID number can appear in different subnets or environments, and the active-status reading belongs to the context that produced it.
Validator Permit Boundary
Active status should not be confused with validator permit status. The glossary describes active UID as a participation slot concept, while validator permit describes authorization for validators to set weights among the qualifying stake-weight group (Glossary: Active UID, Glossary: Validator Permit).
The two signals may appear near each other in subnet discussion, but they answer different questions. Active UID status says whether the slot currently counts as active. Validator permit status says whether a validator is authorized for weight-setting under the validator-permit rules.
Evidence Boundary
An active UID is useful as evidence about participant-slot activity, not as a complete explanation of subnet performance. It does not by itself identify why a participant’s activity status changed, how well a miner is performing, or whether a validator’s weights are useful to the subnet. Those claims need role-specific and mechanism-specific sources.
The same boundary applies to subnet lifecycle claims. Participant activity can change while the subnet continues to exist, whereas subnet deregistration describes removal of an entire subnet context under different rules (Subnet Deregistration).
Relationship to Yuma Consensus
Active UID 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, active uid 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 article explains how to read the active UID concept in a static reference context. It does not count current active UIDs, enumerate subnet participants, diagnose account state, or reproduce interface output. Current readings belong to the relevant subnet, network, block context, and official tooling at the time of observation (Glossary: Active UID, Subnet Metagraph).
Development Stage Context
The Introduction to Bittensor describes subnet development as moving from local testing to testchain and then mainchain. For active UID, that sequence determines which network’s metagraph state is being read.
In local testing, active UID observations reflect a locally running chain’s metagraph state. Localnet activity flags come from local validator weights, subnet rules, and local chain state rather than production Bittensor participant behavior.
On testchain, active UID observations can be read in a shared, non-production network. Testnet
metagraph state shows how activity flags, activity_cutoff, and participant counts behave under
shared chain conditions while staying separate from mainnet participant state.
On mainchain, active UID is the live metagraph flag for participants currently participating in a
production Bittensor subnet. The
Subnet Metagraph reference exposes the active
field per UID, and
Subnet Hyperparameters
defines activity_cutoff as the block-based window that drives the activity boundary
(Glossary: Active UID).
The Bittensor Networks reference separates mainnet, testnet, and localnet. An active UID observation in one environment should not be read as evidence of the same participant activity in another environment.
Runtime Activity Boundary
Active UID status should be read as runtime subnet state rather than a permanent identity label. The metagraph exposes activity in the context of a selected subnet, while subnet hyperparameters describe how activity timing is bounded (Subnet Metagraph, Subnet Hyperparameters).
For readers, that means an active UID claim is strongest when it keeps the netuid, network, and observation time attached. The slot can identify the participant position, but the active flag is evidence from the current subnet state rather than a timeless property of the account.
Active Status Applies to Miners and Validators
The Glossary: Active UID describes an active UID as a subnet slot that allows the associated participant to take part as a subnet validator or subnet miner. The same activity field therefore applies across subnet role types rather than naming only one role label.
Readers should attach the participant role when interpreting an active flag on a subnet such as netuid 1. Active UID answers whether the slot currently counts as participating; miner or validator vocabulary answers which role the slot is being used for (Miners, Validators).