UID Slot
A UID slot is a participant position within a Bittensor subnet. The Glossary: UID Slot describes it as a position occupied by a subnet miner or subnet validator and identified by a unique UID.
Subnet Role
UID slots give subnet participants a position in the subnet context where miner and validator roles are interpreted. The official Miners and Validators pages describe those two roles at a high level: miners produce subnet work, and validators evaluate miner responses.
Slot Capacity and Limits
Each Bittensor subnet has a configurable maximum number of UID slots. The official
Subnet Hyperparameters reference
includes max_allowed_uids as the ceiling for a given subnet. When slots are full, a new
registration can require displacing an existing participant under the miner-deregistration rules
(Mining: Miner deregistration).
For readers, the slot ceiling is a real capacity constraint. Once max_allowed_uids is reached,
accepting a new registrant depends on the official displacement rules.
References: Subnet Hyperparameters, Mining: Miner deregistration
Miner and Validator Roles Share Slot Vocabulary
UID slots organize both subnet miners and subnet validators inside one netuid. The glossary defines a slot as the position a miner or validator occupies, not two separate slot systems for each role. Registration vocabulary therefore grants a participant position inside the subnet regardless of which role the hotkey performs there.
Readers should specify role context when discussing a slot. A UID identifies position inside a subnet; miner and validator documentation describe what work happens from that position after registration succeeds. Role-specific performance, permits, and emissions remain downstream of the slot label itself. Validator permit vocabulary applies only where validating documentation defines permit rules for that netuid. Miner deregistration and validator deregistration describe different role-specific displacement paths when a full subnet must free one slot.
References: Glossary: UID Slot, Miners, Validators
Netuid Scoping for Slot Identity
A UID number names a participant position inside one subnet, not a global identity across every netuid. The same numeric UID can exist on different subnets because netuid selects which subnet market is in scope. Slot language therefore requires pairing UID with netuid whenever readers compare participants across markets.
This scoping prevents a common misread. Observing UID 7 on netuid 3 is not the same participant position as UID 7 on netuid 19. Official glossary entries for netuid and UID slot should be read together when tracing registration, displacement, or activity status on chain. Metagraph queries should always include netuid when resolving a UID slot holder. Cross-subnet comparisons without netuid context are a common source of misread participant identity.
References: Glossary: UID Slot, Glossary: Netuid
Development Stage Context
Subnet development can move from local testing to testchain and then mainchain (Introduction to Bittensor, Bittensor Networks). A UID observed in one environment should not be read as identical evidence about a participant position in another.
For readers, a UID slot is scoped by both netuid and network environment. Production slot readings should keep the selected subnet, environment, and block context attached (Subnet Metagraph).
Register as the Entry Path to a Slot
Register vocabulary describes purchasing a UID slot through the dynamic registration burn on an existing subnet. A UID slot names the position that process grants once entry succeeds. Readers evaluating onboarding should read register as the action and UID slot as the resulting participant position inside the chosen netuid.
That separation mirrors other Taopedia subnet vocabulary pairs. Register does not describe subnet creation at the network level, and a UID slot does not describe how well a participant performs after entry. Live registration costs, immunity timing, and displacement rules belong in official subnet references rather than in a static article quote. Subnet registration at the network level creates netuids; register vocabulary adds participants to an existing netuid.
References: Glossary: Register, Glossary: UID Slot
Relationship to Register
A UID slot and register are related but different parts of Bittensor subnet vocabulary. The Glossary: Register describes the subnet-entry process that gives a participant a UID slot, while the Glossary: UID Slot describes the participant position inside a subnet that entry grants.
For readers, register names the subnet-entry process, while a UID slot names the position a miner or validator occupies after that entry succeeds.
References: Glossary: Register, Glossary: UID Slot
Relationship to Multiple Mechanisms
A UID slot belongs to one subnet context. The Glossary notes that each subnet has one or more incentive mechanisms.
For readers, a UID slot still identifies a participant position inside one subnet market. That subnet may run more than one incentive mechanism, but the slot itself remains subnet-scoped.
References: Multiple Incentive Mechanisms Within Subnets, Glossary: Incentive Mechanism
Relationship to Active UID
A UID slot and an active UID are related but different parts of Bittensor subnet vocabulary. The Glossary: UID Slot describes a participant position inside a subnet, while the Glossary: Active UID describes a slot whose participant is considered active for subnet participation purposes.
For readers, a UID slot names the position itself, while an active UID names activity status within that position. A participant can hold a slot without meeting the activity conditions that make the UID active in metagraph terms.
References: Glossary: UID Slot, Glossary: Active UID
Relationship to Netuid
A UID slot and a netuid are related but different identifiers inside Bittensor subnet vocabulary. A netuid selects which subnet context is in scope, while a UID slot identifies a participant position within that selected subnet. The Glossary: Netuid places netuid at the subnet level, and the Glossary: UID Slot places the slot at the participant level inside one subnet.
For readers, netuid answers which subnet market is being discussed, while a UID slot answers which participant position inside that subnet is meant. The same UID number can appear in different subnets, so slot language must stay paired with the netuid that selects the subnet context.
References: Glossary: Netuid, Glossary: UID Slot
Relationship to Deregistration
A UID slot and deregistration are related but different parts of the subnet participation lifecycle. The Glossary: Deregistration describes the process of removing a participant from a subnet, while the Glossary: UID Slot describes the participant position that process can vacate.
For readers, a UID slot names the occupied position, while deregistration names how a participant can leave that position under subnet rules. When a subnet is at capacity, a new registration may trigger deregistration for an existing slot holder according to official subnet displacement rules.
References: Glossary: Deregistration, Glossary: UID Slot
Relationship to Immunity Period
A UID slot and an immunity period are related through subnet displacement rules. The Glossary: Immunity Period describes a post-registration window during which a participant may be protected from displacement, while the Glossary: UID Slot describes the participant position that protection can apply to.
For readers, a UID slot names the position at stake when a full subnet considers displacement. The immunity period names a timing boundary that can affect whether a newly registered slot holder is eligible to be removed when another participant registers into a full subnet.
References: Glossary: Immunity Period, Glossary: UID Slot, Mining: Miner deregistration
Relationship to Subnet Deregistration
A UID slot and subnet deregistration describe different levels of state. A UID slot is one participant position inside a subnet, while subnet deregistration removes an entire subnet context (Glossary: UID Slot, Subnet Deregistration).
For readers, participant-level deregistration can vacate one UID slot while the subnet continues. Subnet deregistration ends the subnet context that contained the collection of UID slots.
Relationship to Child Hotkeys
A UID slot and a child hotkey describe different parts of validation. A UID slot is the participant position in subnet state, while a child hotkey is a separate key authorized by a parent hotkey (Glossary: UID Slot, Child Hotkeys).
For readers, a parent that holds a slot can authorize a child hotkey to validate for it. The child hotkey is the authorized key, not the slot itself.
Relationship to Yuma Consensus
UID Slot 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, uid slot 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 defines the slot concept. It does not list subnet participants, count occupied slots, or describe current subnet state. Readers should use official subnet references for role-specific details.
Relationship to Coinbase
A UID slot and coinbase are related through subnet rewards, but they name different things. A UID slot is the participant position inside a subnet, while coinbase is the per-block emission operation (Glossary: UID Slot, Coinbase Implementation).
For readers, a UID slot identifies who can be part of subnet reward distribution. Coinbase names part of the mechanism that produces and routes emissions.
Registration Binds the UID to a Hotkey
The Glossary: UID Slot states that the UID is assigned to a hotkey when it registers as a miner or validator. UID slot vocabulary therefore names the participant position inside a subnet, while registration names how that position becomes tied to an operational hotkey (Glossary: Register).
Coldkey authority still governs wallet ownership and stake movement. The slot itself attaches to the hotkey that registered for the subnet role.
Active Status Sits on Top of the Slot
A UID slot identifies participant position, while
active UID status describes whether
that slot currently counts as participating under subnet activity rules. The metagraph exposes an
active field in that subnet context
(Subnet Metagraph).
Readers should not treat slot occupancy and active status as identical claims. A hotkey can hold a UID slot while activity evidence changes with subnet state and timing.