Subnet 40: ?
Subnet 40 is a Bittensor subnet registered on Finney.
On-Chain Identity
The live Finney identity for netuid 40 lists the subnet name as ?. The description, GitHub
repository, project URL, and Discord fields are all blank. No public technical documentation,
codebase, or project description can be sourced from the current on-chain identity alone.
Live subnet data is available on TaoStats.
Miner and Validator Roles
Without a registered GitHub repository or project documentation in the on-chain identity, the subnet-specific miner and validator roles cannot be described reliably. The general Mining and Validating pattern still applies: miners compete for incentive and validators submit weights that feed into Yuma Consensus.
Relationship to Yuma Consensus
Subnet 40 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 40’s on-chain identity lists only the placeholder name ?; the description, GitHub
repository, project URL, and Discord fields are blank. No public source provides a source-verified
description of how validators score miners on Subnet 40. 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 40, that sequence applies to the standard Bittensor lifecycle: localnet for isolated development, testnet for shared non-production testing, and mainnet for live operation with real emissions.
On mainnet, Subnet 40 is registered as the live production subnet at netuid 40. The Bittensor Networks reference separates mainnet, testnet, and localnet. Participation examples or emission outcomes from one environment should not be read as representing production subnet performance in another environment.
Netuid 40 Identifies the Subnet On-Chain
Bittensor assigns every subnet a unique numeric identifier called a netuid, and Subnet 40 is the subnet registered at netuid 40 (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 40 from every other subnet.
For a reader, this means “Subnet 40” and “netuid 40” refer to the same on-chain slot. A claim about Subnet 40 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.
Reader Boundary
Subnet 40 should not be read as generic Bittensor subnet documentation, mining-profitability advice, or a substitute for the subnet’s own primary sources. It names the on-chain subnet slot registered at netuid 40; see this article’s On-Chain Identity section for its current registered fields (Understanding Subnets, Glossary: Netuid).