Subnet Is Active
Subnet is active is a per-subnet flag, listed in the documentation as SubnetIsActive, that
indicates whether a subnet’s emissions have started. The
Subnet Hyperparameters reference
describes it as indicating whether or not the subnet’s emissions have started, which separates a
subnet that merely exists on-chain from one that is live and emitting.
What It Controls
The flag reports emission startup status, not registration rights or subnet existence. A netuid can already expose registered neurons, hyperparameter rows, and metagraph state while the flag remains false, meaning the subnet’s emission distribution path has not yet started. Registration, subnet configuration, and validator weight submission can still proceed on that netuid, but the subnet is not yet allocating from its emission pool until activation occurs, so roster presence alone is not proof that emissions are flowing (Subnet Hyperparameters, Emission).
Distinction from Start Call
Start call is the action that begins a subnet’s emissions, while subnet is active is the resulting state that reports whether those emissions have started. One is the trigger; the other is the status it produces (Emission, Subnet Hyperparameters).
- Start call — the operation that switches a subnet’s emissions on.
- Subnet is active — the flag that reports emissions have started.
Distinction from Registration Allowed
Registration allowed governs whether new neurons can register on a subnet, while subnet is active reports whether the subnet is emitting. A subnet can be registered and configured without yet emitting, so the two answer different questions (Subnet Hyperparameters).
- Registration allowed — whether new neurons may join the subnet.
- Subnet is active — whether the subnet’s emissions have started.
Distinction from Netuid
Subnet is active reports whether a subnet’s emissions have started on a netuid such as netuid 1. Netuid names the subnet slot itself, which can exist before emissions begin (Subnet Hyperparameters, Glossary: Netuid, Emission).
A subnet can exist at a netuid before its emission path starts. The active flag marks when that path has begun.
- Subnet is active — whether emissions have started on the netuid.
- Netuid — the subnet identifier whose emission status is being read.
Distinction from Emission
Subnet is active is the boolean flag that reports whether a subnet’s emission path has started. Emission is the broader reward flow that distributes alpha once that path is live (Subnet Hyperparameters, Glossary: Emission, Emission).
The flag reports status. Emission describes the reward mechanism that runs once status is active.
- Subnet is active — whether the subnet’s emission path has started.
- Emission — the reward flow that distributes alpha on active subnets.
Distinction from Subnet Symbol
Subnet is active and subnet symbol are both subnet-level concepts, illustrated here on a subnet such as netuid 1, but they describe entirely different things. Subnet is active is the boolean flag for whether a subnet’s emissions have started, while subnet symbol is the written character used to denote that subnet’s token in interfaces. One is an emission-status indicator; the other is a display label for the subnet’s currency (Emission, Understanding Subnets).
- Subnet is active — whether the subnet’s emissions have started.
- Subnet symbol — the written character denoting the subnet’s token.
Distinction from Subnet Emission Enabled
Subnet is active reports whether a subnet’s emission path has started. Subnet emission enabled is the separate root-governance toggle that can halt pool-side injection on an already-active subnet without dissolving it (Subnet Hyperparameters, Emission).
- Subnet is active — whether the subnet’s emissions have started.
- Subnet emission enabled — whether pool-side injection runs each epoch on an active subnet.
Distinction from Subnet Owner Take
Subnet is active and subnet owner take describe an emission status and an emission share, illustrated here on a subnet such as netuid 1. Subnet is active reports whether a subnet’s emissions have started, while subnet owner take is the documented portion of those emissions allocated to the subnet owner. The flag answers whether emission is flowing; the take answers how much of it goes to the owner once it does (Emission, Emission: Distribution).
- Subnet is active — whether the subnet’s emissions have started.
- Subnet owner take — the owner’s share of those emissions once they flow.
Chain Reads for netuid 1
Readers can verify live hyperparameter values for the documented example netuid with
btcli subnet hyperparameters --netuid 1 --network finney
(Subnet Hyperparameters: View hyperparameters).
That read path keeps live hyperparameter claims tied to a parseable netuid.
Per-Subnet Live Value Boundary
Subnet is active is per-subnet chain state. The flag on one netuid reports whether that subnet’s emission path has started, but the live status can differ from reference defaults and from the flag on another netuid (Subnet Hyperparameters, Emission).
This article’s infobox uses netuid 1 as an example label when reading one subnet’s hyperparameter row on Finney mainnet. That example helps readers verify one table; it is not proof that every subnet exposes the same live emission status (Bittensor Networks).
Subnet is active governs emission startup status; Yuma Consensus still converts validator weights into emission shares each tempo on active subnets (Yuma Consensus).
- Subnet is active — whether the subnet’s emission path has started on a netuid.
- Per-subnet boundary — live value is chain state on one netuid.
Distinction from Yuma Consensus
Subnet is active names the boolean hyperparameter that reports whether a subnet’s emission path has started. Yuma Consensus is the separate mechanism that converts validator weight submissions into emission shares each tempo on active subnets (Yuma Consensus, Emission, Subnet Hyperparameters).
-
Subnet is active — whether the subnet’s emissions have started.
-
Yuma Consensus — on-chain settlement that turns validator weights into emission shares. Subnet is active names whether emissions have started; Yuma processes validator weights into rewards (Yuma Consensus: Validator emissions).
-
Status vs slot — a netuid can exist before its emission path starts (Subnet Hyperparameters, Emission).
-
Related gates — registration allowed and start call are separate controls on the same netuid (Subnet Hyperparameters).
Reader Boundary
Subnet is active should not be read as a registration gate, an emission amount, or proof that a subnet is profitable. It names only the boolean flag that reports whether the subnet’s emission path has started on the selected netuid (Subnet Hyperparameters).