Subnet 86: ⚒
⚒ is Bittensor Subnet 86.
What ⚒ Provides
Public technical documentation for ⚒ is not available through the on-chain identity alone. The GitHub repository, project URL, and Discord fields are blank on Finney. The description field is registered but does not document a subnet protocol or project.
Miner and Validator Roles
Subnet 86 operates under the standard Bittensor two-role structure. Miners supply a capability to the network, and validators evaluate those contributions and set weights. Those weights feed into Yuma Consensus, which converts validator assessments into emissions that reward the strongest performers.
On-Chain Identity
The on-chain identity for netuid 86 lists the subnet name as ”⚒”. The GitHub repository, project URL, and Discord fields are blank. Live identity data is available on TaoStats.
Relationship to Yuma Consensus
Subnet 86 uses 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 86’s live Finney identity lists only the ⚒ symbol with the GitHub, URL, and Discord fields blank, 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 86 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 86, 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 86 is registered as the live production subnet at netuid 86. 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.
Reader Boundary
Subnet 86 should not be read as generic Bittensor subnet documentation, an active public protocol description, or proof of a reproducible miner task on netuid 86. Its live Finney identity lists the subnet name as ⚒ with blank GitHub, URL, and Discord fields, so Taopedia cannot source miner and validator behavior beyond the generic Bittensor role model (btcli reference).
Blank Repository Fields Block Mechanism Claims
Readers should treat this page as identity-state reporting and verify the current on-chain identity before relying on any description, because subnet operators can update identity fields over time. Until a real repository or mechanism spec is registered on-chain, statements about Subnet 86’s specific scoring logic or task output would be speculative.
The Registered Symbol Is Not a Protocol Description
The ⚒ subnet name is an on-chain label, not a substitute for README or website documentation. If a future operator registers project links and a mechanism description, that registered source should replace placeholder summaries as the basis for a revised article.
Validator weights still flow through Yuma Consensus to determine emissions each tempo (Yuma Consensus, Emission).