Subnet 87: unknown
Subnet 87 is Bittensor Subnet 87.
What Subnet 87 Provides
Public technical documentation for Subnet 87 is not available through the on-chain identity alone. The description, GitHub repository, project URL, and Discord fields are all blank on Finney at the time of writing.
Miner and Validator Roles
Subnet 87 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 87 lists the subnet name as “unknown.” All other identity fields — description, GitHub repository, project URL, and Discord — are blank. Live identity data is available on TaoStats.
Relationship to Yuma Consensus
Subnet 87 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 87’s live Finney identity lists the name as “unknown” with all other identity 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 87 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 87, 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 87 is registered as the live production subnet at netuid 87. 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 87 should not be read as generic Bittensor subnet documentation, an active public protocol description, or proof of a reproducible miner task on netuid 87. Its live Finney identity lists the subnet name as “unknown” with blank description, GitHub, URL, and Discord fields, so Taopedia cannot source miner and validator behavior beyond the generic Bittensor role model (btcli reference).
Blank Identity 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 87’s specific scoring logic or task output would be speculative.
The “unknown” Label Is Not a Project Description
The registered subnet name reflects missing public metadata, not an invitation to infer purpose from third-party rumors or unrelated netuid articles. If a future operator registers a named project with documentation, 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).