Subnet 39: Deprecated
Subnet 39 is a Bittensor subnet slot whose current on-chain identity is registered as “deprecated.” The live identity does not present an active public protocol, miner task, validator task, or project documentation. Instead, the registered subnet name, description, and Discord field all read “deprecated.”
The registered GitHub field contains a deprecated/deprecated placeholder path, and the subnet URL
field is blank. Readers should therefore treat Subnet 39 as a deprecated slot rather than as an
active subnet with a reproducible public codebase or current operator documentation.
Current Status
For active subnet articles, Taopedia normally describes what miners do, how validators score them, and which repository or documentation defines the mechanism. Subnet 39 does not currently expose that kind of public implementation source through its live identity fields.
The useful fact about Subnet 39 is its registered state. A future operator could update the subnet’s identity and publish new documentation, so readers should verify the live Finney identity before relying on this page.
On-Chain Identity
Live SN39 data is available on TaoStats. Readers can reproduce the
subnet’s registered identity fields with the Bittensor CLI command documented in the
btcli reference:
btcli subnets get-identity --netuid 39 --network finney.
That Finney identity reports the subnet name and description as “deprecated.” It also reports a
deprecated/deprecated placeholder path for the GitHub field, a blank subnet URL, deprecated for
Discord, deprecated@gmail.com for contact, and a placeholder logo field.
Relationship to Yuma Consensus
Subnet 39 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 39’s on-chain identity registers the subnet name, description, and Discord field all as “deprecated,” with no active public protocol, miner task, or validator documentation. No public source provides a source-verified description of how validators score miners on Subnet 39. 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 39, 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 39 is registered as a deprecated slot at netuid 39. 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 39 Identifies the Subnet On-Chain
Bittensor assigns every subnet a unique numeric identifier called a netuid, and Subnet 39 is the subnet registered at netuid 39 (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 39 from every other subnet.
For a reader, this means “Subnet 39” and “netuid 39” refer to the same on-chain slot. A claim about Subnet 39 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 39 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 39 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 39; see this article’s On-Chain Identity section for its current registered fields (Understanding Subnets, Glossary: Netuid).