Register
Register is the subnet-entry process that gives a Bittensor participant a UID slot inside a subnet. The official Glossary defines it as registering with a subnet and purchasing a UID slot by paying a dynamic registration burn in TAO.
UID Slot Context
Registration matters because subnet participation is organized around UID slots. The Glossary: UID Slot entry defines a UID slot as a position occupied by a subnet miner or subnet validator within a subnet. In practical reading, register is the step that connects a participant to that subnet position.
The official Mining documentation uses miner registration as a concrete example: a miner must register with a subnet to receive a UID on that subnet. This article keeps the concept at that level rather than expanding into operational steps.
Dynamic Registration Burn
Register has a cost context. The Glossary describes the registration burn as dynamic, with bounds and adjustment behavior controlled by subnet parameters. The Mining documentation also describes the cost as changing over time.
For Taopedia readers, the important point is not a current number. It is that registration is a subnet-entry action with a dynamic TAO cost, so static articles should not quote a current registration price.
Burn Price Bounds and Decay
The official Glossary: Register
describes the neuron registration burn as dynamic with explicit parameter bounds. The burn price is
bounded by MinBurn and MaxBurn, decays over time according to BurnHalfLife, and increases on
each successful registration through BurnIncreaseMult.
That parameter set explains why registration cost is neither fixed nor arbitrary. The price falls when registrations are quiet and rises when slots fill, while the bounds keep the burn inside subnet hyperparameter limits. Static articles should describe that adjustment behavior rather than quoting a live registration amount.
References: Glossary: Register, Mining: Miner registration
Alpha Pool Recycling From Registration Fees
Neuron registration fees are paid in TAO, but the fee also interacts with subnet pool accounting. Official glossary wording states that alpha tokens worth the current swap value of the registration fee are taken from the subnet’s alpha liquidity pool and recycled when a hotkey registers on a subnet.
For readers, register therefore connects subnet entry to Dynamic TAO pool mechanics, not only to a UID assignment. The burn is a TAO payment, while the recycling step moves equivalent alpha value out of the subnet pool context described in subnet liquidity documentation.
References: Glossary: Register, Understanding Subnets
Register and Burned_Register Extrinsics
The glossary notes that the register and burned_register extrinsics share the same non-root burn
path for subnet entry. Both routes purchase a UID slot through the dynamic registration burn rather
than describing separate admission economics for ordinary subnets.
Root registration is treated separately in official documentation. When reading register at Taopedia level, the shared non-root burn path keeps miner and validator registration examples aligned on the same subnet-entry cost model unless the article explicitly discusses Subnet Zero.
References: Glossary: Register, Subtensor extrinsics
Relationship to Deregistration
Registration and deregistration are opposite sides of subnet capacity. Registration adds a participant to a UID slot, while deregistration removes an eligible low-performing participant from a slot when subnet capacity and replacement rules require it. The official Mining documentation places deregistration in the context of a new registration arriving when a subnet is full.
This relationship does not mean every registration removes another participant. It means the term should be read in the context of finite subnet UID slots and the subnet’s participation rules.
Relationship to Miner Registration
Register and miner registration address related but different scopes in Bittensor subnet vocabulary. The Glossary: Register describes subnet entry as purchasing a UID slot through a dynamic registration burn in TAO, while Mining: Miner registration describes that entry process applied to a subnet miner who will take part in mining work and evaluation.
For readers, register is the general subnet-entry term, while miner registration names the miner-specific case of that process.
References: Glossary: Register, Mining: Miner registration
Relationship to Validator Registration
Register and validator registration address related but different scopes in Bittensor subnet vocabulary. The Glossary: Register describes subnet entry as purchasing a UID slot through a dynamic registration burn in TAO, while Validating: Validator registration describes that entry process applied to a subnet validator who will take part in evaluation and validation work.
For readers, register is the general subnet-entry term, while validator registration names the validator-specific case of that process.
References: Glossary: Register, Validating: Validator registration
Relationship to Multiple Mechanisms
Register gives a participant a UID slot inside a subnet. The Glossary notes that validators must evaluate miners separately for each mechanism.
For readers, registration still names subnet entry into a UID slot. When that subnet runs more than one incentive mechanism, evaluation after registration happens under separate mechanism contexts.
References: Multiple Incentive Mechanisms Within Subnets, Glossary: Multiple Incentive Mechanisms
Relationship to UID Slot
Register and a UID slot are related but different parts of Bittensor subnet registration vocabulary. The Glossary: Register describes the subnet-entry process that grants a participant a UID slot, while the Glossary: UID Slot describes the participant position inside a subnet that entry provides.
For readers, register names the 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 Netuid
Register and a netuid are related but different parts of Bittensor subnet vocabulary. Register describes the subnet-entry process that grants a UID slot, while a netuid selects which subnet that entry targets. The Glossary: Register describes subnet entry, and the Glossary: Netuid places netuid at the subnet-selection level.
For readers, register names how a participant enters a subnet, while a netuid names which subnet market that entry applies to. Registration language is incomplete without the netuid that selects the destination subnet context.
References: Glossary: Register, Glossary: Netuid
Relationship to Immunity Period
Register and an immunity period are related but different parts of the subnet participation lifecycle. The Glossary: Register describes the subnet-entry process, while the Glossary: Immunity Period describes a temporary protection window that begins after a participant registers into a subnet.
For readers, register names the entry event, while immunity period names the grace window that can follow that entry before ordinary low-performance removal rules apply.
References: Glossary: Register, Glossary: Immunity Period
Relationship to Active UID
Register and an active UID are related but different parts of the subnet participation lifecycle. Register describes the subnet-entry process that grants a UID slot, while an active UID describes ongoing activity status after a participant already holds a slot. The Glossary: Register describes subnet entry, and the Glossary: Active UID describes a slot whose participant is considered active for subnet participation purposes.
For readers, register names how a participant enters a subnet, while an active UID names whether that slot currently meets the activity conditions tracked on the metagraph after entry.
References: Glossary: Register, Glossary: Active UID
Relationship to Child Hotkeys
Register and child hotkeys both relate to taking part in a subnet, but they describe different steps. Register is the subnet-entry process that gives a hotkey a UID slot by paying a dynamic registration burn in TAO, as the Glossary: Register defines it. Child-hotkey configuration, by the Child Hotkeys documentation, lets a registered parent hotkey allocate a portion of its stake-weight to one or more child hotkeys for validation, where those child hotkeys must already be registered on the netuid on which they validate.
For readers, register answers how a hotkey obtains a UID slot in a subnet, while child-hotkey configuration answers how a registered parent assigns stake-weight to other registered hotkeys to validate on its behalf. The two are not opposites: a child hotkey still needs its own registration on the netuid, and child-hotkey configuration is the separate step that re-delegates a parent’s stake-weight to those already-registered child hotkeys. Register places a hotkey in the subnet with a UID slot; child-hotkey configuration arranges validation duties among registered hotkeys.
References: Glossary: Register, Child Hotkeys
Relationship to Yuma Consensus
Register 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, register 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
Register should be read as a concept about entering subnet participation. It is not a current cost quote, a guarantee of future rewards, or a status report on any specific subnet’s available capacity. Exact registration steps, prices, and subnet-specific details belong in the current official documentation.
Relationship to Coinbase
Register and coinbase are related through subnet participation, but they name different things. Register is the subnet-entry process that grants a UID slot, while coinbase is the per-block emission operation (Glossary: Register, Coinbase Implementation).
For readers, registration places a participant into the UID slot set that later epoch processing can consider. It does not by itself guarantee emissions; rewards still depend on activity, validator evaluations, stake, and runtime logic.
Development Stage Context
Subnet development can move from localnet to testnet and then mainnet (Introduction to Bittensor, Bittensor Networks). A registration example from one environment should not be read as representing UID state or burn costs in another.
For readers, local and testnet registration examples are useful for context, but mainnet registration is the live Subtensor operation that purchases a UID slot through the dynamic burn (Glossary: Register).
Subnet Entry Boundary
Register should be read as subnet entry, not as a general account creation event. The glossary defines registration around purchasing a UID slot with a dynamic registration burn, and mining documentation uses miner registration as a concrete subnet-entry example (Glossary: Register, Mining: Miner registration).
For readers, the claim should keep the selected subnet visible. Registering for one subnet grants a UID slot in that subnet context; it does not imply the same role or slot across every subnet.