Subnet 106: Nodexo
Nodexo is Bittensor Subnet 106. The live Finney identity registers the subnet name as “Nodexo” with the description “tokenized ai compute.” The identity fields list a GitHub address (neuralinternet/SN27) and a project URL (nodexo.ai), but neither resolved to a publicly accessible resource at the time this article was updated.
Because no accessible public source currently describes the subnet mechanism, this page does not state what miners produce, how validators score submissions, or how the subnet distributes rewards beyond what the chain identity provides.
On-Chain Identity
The current Finney identity for netuid 106 reports the name “Nodexo,” the description “tokenized ai compute,” a GitHub field pointing to neuralinternet/SN27, a URL field for nodexo.ai, and a Discord field. Live data is available on TaoStats.
Relationship to Yuma Consensus
Subnet 106 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 repo and project URL listed in Subnet 106’s on-chain identity did not resolve to a publicly accessible source describing how validators score miners or what weight vectors represent 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 Nodexo (SN106), 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, Nodexo (SN106) is registered as the live production subnet at netuid 106. 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 106 Identifies the Subnet On-Chain
Bittensor assigns every subnet a unique numeric identifier called a netuid, and Subnet 106 is the subnet registered at netuid 106 (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 Nodexo from every other subnet even when its other identity fields are sparse.
For a reader, this means “Subnet 106” and “netuid 106” refer to the same on-chain slot. A claim about Nodexo 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.
Miner and Validator Roles
Subnet 106 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 106 Nodexo should not be read as generic Bittensor subnet documentation, confirmation that its listed GitHub repository or website is live, or proof that the subnet has a published miner and validator mechanism. It names one on-chain subnet slot registered at netuid 106 with the description “tokenized ai compute” (Understanding Subnets, Glossary: Netuid).