Subnet 81: Deprecated
Subnet 81 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 description, Discord field, and subnet name 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 81 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 81 does not currently expose that kind of public implementation source through its live identity fields.
The useful fact about Subnet 81 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 SN81 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 81 --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 81 is registered on Bittensor and would use Yuma Consensus to convert validator weight vectors into the emission shares distributed to miners and validators within the subnet each tempo. The Yuma Consensus documentation describes how validator weight submissions are aggregated into consensus weights for each miner registered on the subnet.
Because Subnet 81’s current identity is registered as “deprecated” with placeholder GitHub and Discord fields and no active public protocol documentation, no source-backed description of how validators score miners or what weight vectors represent is available. The Emission documentation describes how consensus weights determine each participant’s share of the subnet’s accumulated emission each tempo, and those mechanics apply to Subnet 81 once a source-backed incentive mechanism is established.
Development Stage Context
The Introduction to Bittensor describes subnet development as moving from localnet to testnet and then mainnet. For Subnet 81, 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 81 is registered as the live production subnet at netuid 81. 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.
Miner and Validator Roles
Subnet 81 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 81 should not be read as generic Bittensor subnet documentation, an active public protocol description, or proof of a reproducible miner task on netuid 81. Its live Finney identity is registered as “deprecated” with placeholder GitHub, Discord, and contact fields rather than an active project repository (btcli reference).
Identity-State Reporting Replaces Mechanism Detail
This article reports the subnet’s registered identity fields through TaoStats and the Bittensor CLI because no source-backed README or website defines how validators would score miners today. Readers should verify the current on-chain identity before relying on any description, since a future operator could replace the deprecated registration with new metadata and documentation.
No Source-Backed Scoring Claims Until Identity Updates
Until a real repository or mechanism spec is registered on-chain, statements about Subnet 81’s specific weight logic or task output would be speculative. Validator weights still flow through Yuma Consensus to determine emissions each tempo for any registered subnet slot (Yuma Consensus, Emission), but Taopedia cannot document miner or validator behavior beyond that generic model for this deprecated registration.