Subnet 116: Unknown
Subnet 116 is a Bittensor subnet with no registered on-chain identity.
What Subnet 116 Provides
The Finney identity query for netuid 116 returns no registered project information. The subnet name, description, GitHub repository, project URL, and Discord fields are all absent from the on-chain record.
Miner and Validator Roles
Subnet 116 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 Finney identity query for netuid 116 returns no registered identity record. All fields — subnet name, description, GitHub repository, project URL, and Discord — are absent. Live subnet data is available on TaoStats.
Relationship to Yuma Consensus
Subnet 116 is registered on Bittensor and 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 116 has no registered on-chain identity and no public source describing how validators score miners, no source-backed description of its incentive mechanism is available. 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 116, 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 116 is registered as the live production subnet at netuid 116. 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 116 should not be read as a named project subnet with a published incentive mechanism. The Finney identity query for netuid 116 returns no registered subnet name, description, GitHub repository, project URL, or Discord contact, so Taopedia cannot describe subnet-specific scoring rules beyond what the chain identity record contains.
No Registered Project Identity on Finney
Live data on TaoStats can show registration and emission activity, but absent identity fields mean readers should not infer a particular product, codebase, or validator rubric from the article alone. Any mechanism claims require a future on-chain identity update or linked public source.
Standard Roles Without Public Scoring Specification
Subnet 116 still follows the usual Bittensor miner-and-validator structure, with validators setting weights that flow through Yuma Consensus. Without a public README or registered repository, however, the article cannot state what capability miners supply or how validators score it.
Validator weights still flow through Yuma Consensus to determine emissions each tempo (Yuma Consensus, Emission).