Subnet 117: Unknown
Subnet 117 is a Bittensor subnet registered on Finney with the name Unknown.
What Subnet 117 Provides
Public technical documentation for Subnet 117 is not available through the on-chain identity alone.
The on-chain identity lists a GitHub repository for helionlink/Chi, but the description, project
URL, and Discord fields are each set to ~ and carry no substantive information.
Miner and Validator Roles
The subnet-specific miner and validator roles cannot be described reliably from the registered identity fields alone. At the Bittensor level, miners compete for incentive and validators submit weights that feed into Yuma Consensus, but Subnet 117’s public identity does not specify the task that distinguishes this subnet.
On-Chain Identity
The on-chain identity for netuid 117 lists the subnet name as Unknown. The GitHub field references
helionlink/Chi. The description, project URL, and Discord
fields are each set to the placeholder value ~. Live identity data is available on
TaoStats.
Relationship to Yuma Consensus
Subnet 117 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.
The GitHub repository listed in Subnet 117’s on-chain identity (helionlink/Chi) did not resolve to a publicly accessible source describing how validators score miners at the time this article was updated. 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 117, 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 117 is registered as the live production subnet at netuid 117. 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 117 Identifies the Subnet On-Chain
Bittensor assigns every subnet a unique numeric identifier called a netuid, and Subnet 117 is the subnet registered at netuid 117 (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 117 from every other subnet.
For a reader, this means “Subnet 117” and “netuid 117” refer to the same on-chain slot. A claim about Subnet 117 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.
Reader Boundary
Subnet 117 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 117; see this article’s On-Chain Identity section for its current registered fields (Understanding Subnets, Glossary: Netuid).