Subnet 3: Deprecated
Subnet 3 (netuid 3) is a slot on the Bittensor network whose on-chain identity description reads “deprecated.” The registered GitHub and URL fields both contain generic placeholder values rather than active resources. No public codebase or documentation is available through those registered identifiers.
The subnet’s alpha-token pool continues to exist on-chain. Pool state, the registered owner coldkey, and current neuron count are verifiable via taostats.io/subnets/3.
On-Chain Identity
Subnet 3’s registered on-chain identity, verifiable via taostats.io/subnets/3:
- Description: deprecated
- Owner coldkey:
5FUJoAsY5TWfs1FGFtscC5QUuarJMCWYwYzEftyGAeH7pUqK(view on taostats) - GitHub: placeholder (no active repository)
- URL: placeholder (no active site)
- Discord: deprecated
- Neurons: 256
Relationship to Yuma Consensus
Subnet 3 uses Yuma Consensus to convert validator weight vectors into the emission shares distributed to miners and validators within the subnet each tempo. The linked documentation describes how validator weight submissions are aggregated into consensus weights for each miner registered on the subnet.
Subnet 3’s on-chain identity description reads “deprecated,” and no public source describes how validators score miners on Subnet 3. The Emission documentation describes how consensus weights determine each participant’s share of the subnet’s accumulated emission each tempo.
Development Stage Context
The Introduction to Bittensor describes subnet development as moving from localnet to testnet and then mainnet. For Subnet 3, that sequence is relevant in one direction: the on-chain slot, pool state, and identity metadata described in this article reflect the current production mainnet state of netuid 3, which is registered as deprecated.
The Bittensor Networks reference separates mainnet, testnet, and localnet. On-chain identity data for netuid 3 should be read as mainnet state. Pool state or owner coldkey information observed on testnet or localnet would belong to those environments and would not represent the mainnet registration described here.
Netuid 3 Identifies the Subnet On-Chain
Bittensor assigns every subnet a unique numeric identifier called a netuid, and Subnet 3 is the subnet registered at netuid 3 (Glossary: Netuid). The Understanding Subnets reference explains that each subnet runs its own incentive mechanism while sharing the same underlying Subtensor chain, so the netuid is the stable handle that distinguishes Subnet 3 from every other subnet.
For a reader, this means “Subnet 3” and “netuid 3” refer to the same on-chain slot. A claim about Subnet 3 should be tied to that netuid rather than to the registered name alone, because the name field can be changed on-chain while the netuid stays fixed.
Miner and Validator Roles
Subnet 3 operates under the standard Bittensor two-role structure. Miners supply the subnet’s capability and validators evaluate those contributions and set weights. Reward distribution follows Yuma Consensus.
Reader Boundary
Subnet 3 should not be read as generic Bittensor subnet documentation, confirmation that the subnet has a published, working mechanism, or a substitute for the subnet’s own primary sources. It names the on-chain subnet slot registered at netuid 3; see this article’s On-Chain Identity section for its current registered fields (Understanding Subnets, Glossary: Netuid).