Subnet Registration
Subnet registration is the process of creating a new subnet on the Bittensor network. The Subnet Registration documentation describes it as the step where a participant pays a registration burn to open a new incentive market, and the Glossary: Burn Cost defines that burn as the cost of registering a new subnet.
In Taopedia terms, subnet registration names a creation process, not a participant role or a token amount. It is distinct from neuron registration, which adds a miner or validator to an existing subnet rather than creating a new one.
Why Subnet Registration Exists
Bittensor is organized around subnets, each running its own incentive mechanism for a specific kind of work. Understanding Subnets explains that the network grows by adding new subnet markets, and subnet registration is the process that opens them.
For readers, subnet registration is best understood as the network-expansion step. Without it, no new subnet markets would appear. The registration burn is the mechanism’s way of making creation deliberate rather than free, so that new subnets represent a committed investment.
References: Understanding Subnets, Subnet Registration
What Subnet Registration Does
Subnet registration takes a registration burn from the participant and produces a new subnet. The Glossary: Burn Cost describes the burn as TAO that is recycled when a new subnet is created, and the Recycling and burning glossary entry explains that recycled tokens are subtracted from total issuance so they can be emitted again.
For readers, the important behavior is that subnet registration converts a TAO burn into a new subnet identity. The new subnet receives a unique netuid, begins participating in the network’s incentive structure, and becomes a destination for staking and emission activity.
References: Glossary: Burn Cost, Recycling and burning
Relationship to Register
Subnet registration and register are related but different registration concepts. The Glossary: Register describes register as purchasing a UID slot on an existing subnet by paying a neuron registration burn, while subnet registration creates an entirely new subnet.
For readers, register names the process of joining an existing subnet as a miner or validator, while subnet registration names the process of creating a new subnet for others to join. The two are different creation events at different levels of the network.
References: Glossary: Register, Glossary: Burn Cost
Relationship to Burn Cost
Subnet registration and burn cost are related because the burn is what subnet registration requires. The Glossary: Burn Cost defines burn cost as the TAO required to create a new subnet, and subnet registration is the process that pays it.
For readers, burn cost names the price of creating a subnet, while subnet registration names the act of paying that price to open the subnet. One names the cost and the other names the process, so they should not be read as interchangeable.
References: Glossary: Burn Cost
Relationship to Subnet Creator
Subnet registration and the subnet creator are related because the creator is the participant who performs the registration. The Glossary: Subnet Creator describes the subnet creator as the entity responsible for defining the subnet’s task and incentive mechanism, and subnet registration is the step that brings that subnet into existence.
For readers, subnet creator names the participant role, while subnet registration names the creation process that role performs. The creator defines what the subnet does; registration makes it exist on the network.
References: Glossary: Subnet Creator, Subnet Registration
Relationship to Netuid
Subnet registration and netuid are related because registration produces a new netuid. The Glossary: Netuid describes a netuid as the unique identifier assigned to a subnet, and subnet registration is the event that assigns it.
For readers, netuid names the identifier a subnet receives, while subnet registration names the process that creates the subnet and triggers that assignment. The netuid is the result; registration is the cause.
References: Glossary: Netuid
Relationship to Subnet Lease
Subnet registration can be performed in two ways that the official docs distinguish. A creator can
fund a new subnet directly, or a creator can fund it indirectly through a crowdloan, which the
Crowdloans documentation describes as the
funding path that ends in a subtensor::register_leased_network call. When registration happens
through that path, the registration produces both a new subnet and a subnet lease, which the same
source defines as “split profit ownership of a subnet” — the crowdloan creator becomes the lease
beneficiary and the crowdloan contributors become the lease shareholders.
For readers, subnet registration names the act of creating a subnet, while a subnet lease names the profit-sharing arrangement that can come with a crowdloan-funded subnet. Not every subnet registration produces a lease: a creator who funds a subnet directly creates the subnet without the lease structure. When a crowdloan funds the registration, the lease is the layered ownership arrangement the crowdloan produces on top of the new subnet.
References: Crowdloans documentation, Subnet Registration
Relationship to Subnet Deregistration
Subnet registration and subnet deregistration sit at opposite ends of the subnet lifecycle. Subnet registration is the process of creating a new subnet by paying a registration burn to receive a unique netuid and open a new incentive market, while subnet deregistration is the mechanism that removes an entire non-immune subnet from the network when the subnet limit is reached and a new subnet registration attempts to enter, selecting the subnet with the lowest EMA of alpha price for removal. The Subnet Registration documentation describes subnet registration as the creation process, and the Subnet Deregistration documentation describes subnet deregistration as the removal process that the registration attempt triggers when the network is at capacity.
A new subnet registration attempt is the event that can trigger subnet deregistration — but only when the current subnet count is already at the network’s subnet limit. When a new registration proceeds under those conditions, the existing subnet with the lowest EMA of alpha price is removed to make room for the incoming subnet. The newly registered subnet then receives an immunity period, which protects it from being immediately selected as a candidate for future subnet deregistration. Subnet registration creates; subnet deregistration removes — and a registration is the specific trigger that causes removal to occur when the network has no free slot to accommodate a new subnet.
References: Subnet Registration, Subnet Deregistration, Glossary: Immunity Period
Reader Boundary
This article defines subnet registration as a concept. It does not state current burn amounts, describe registration steps, list active subnets, or compare subnet-creation strategies. Readers should use the official subnet documentation for operational detail and current costs.
Relationship to Coinbase
Subnet registration and coinbase are related but different parts of Bittensor’s subnet lifecycle and emission machinery. Subnet registration is the process of creating a new subnet by paying a registration burn to receive a unique netuid and open a new incentive market. Coinbase is the per-block protocol mechanism that drives TAO emission, injects TAO into subnet pool reserves each block, accumulates pending emissions, and checks epoch boundaries to trigger Yuma Consensus rounds. The Subnet Registration documentation describes the creation process, and the Coinbase Implementation documentation describes the per-block emission operation.
Subnet registration is what brings a subnet into existence; coinbase is what drives emissions through that subnet once it exists. A newly registered subnet receives a netuid and becomes a destination for the per-block reserve injection and pending-emission accumulation that coinbase performs. Once the subnet’s epoch boundary is reached, coinbase triggers the Yuma Consensus round that distributes that subnet’s accumulated emissions among its miners, validators, and stakers. Registration opens the market; coinbase supplies and distributes the emissions that flow through it each block and epoch.
Development Stage Context
The Introduction to Bittensor describes subnet development as moving from localnet to testnet and then mainnet. For subnet registration, that sequence changes how readers should interpret examples of subnet creation and burn-cost outcomes.
In localnet, subnet registration can be exercised in an isolated environment. Localnet registration events reflect local chain state and locally configured burn-cost parameters rather than production subnet creation.
On testnet, subnet registration can be observed in a shared, non-production network. Testnet registration shows how burn-cost, recycle behavior, and subnet identity fields behave under shared chain conditions while staying separate from mainnet subnet state.
On mainnet, subnet registration is the live action that brings a new subnet into the production Bittensor network. The Create a Subnet reference describes the subnet-creation flow that applies on the production network, and the Burn Cost glossary entry explains the recycled TAO component of the registration cost.
The Bittensor Networks reference separates mainnet, testnet, and localnet. A subnet registration observed in one environment should not be read as evidence of production subnet creation in another environment.
Direct Creation Differs From Crowdloan-Funded Registration
The Create a Subnet path describes a creator funding subnet registration directly, while Crowdloans documentation describes collective funding that can finalize into a leased subnet. Subnet registration names the creation event in both cases, but only the crowdloan path also produces the lease structure described in crowdloan material.
Readers comparing funding models should keep registration vocabulary separate from lease profit-sharing vocabulary. Registration opens the subnet; crowdloan finalization adds beneficiary and shareholder roles when that funding path succeeds.