Subnet 122: CookingTAO
CookingTAO is Bittensor Subnet 122.
What CookingTAO Provides
The on-chain description states “Democratizing Bittensor Mining.” The registered project website is cookingtao.com. Additional public technical documentation for the specific subnet mechanism is not available through the on-chain identity alone.
Miner and Validator Roles
Subnet 122 operates under the standard Bittensor two-role structure. Miners supply a capability to the network, and validators evaluate those contributions and assign weights. Those weights feed into Yuma Consensus, which converts validator assessments into emissions that reward the strongest performers.
The general miner-validator relationship is described in Understanding Subnets: miners produce work for a subnet, and validators measure that work against the subnet’s standards.
On-Chain Identity
The live Finney identity for netuid 122 registers the subnet name as CookingTAO and the description as “Democratizing Bittensor Mining.” The registered website is cookingtao.com and the GitHub organization is github.com/CookingTao. The Discord field is blank. Live subnet data is available on TaoStats.
Public Information
Public information confirms CookingTAO’s registered identity, website, GitHub organization, and broad “Democratizing Bittensor Mining” description. No public CookingTAO-specific miner task, validator prompt set, scoring rule, or reward criterion was found in the cited sources, so the available sources support an identity-level profile rather than a detailed mechanism description.
Relationship to Yuma Consensus
Subnet 122 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.
CookingTAO’s on-chain identity lists a website and GitHub organization but does not provide a source-verified description of the specific validator scoring mechanics for Subnet 122. 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 CookingTAO (SN122), 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, CookingTAO (SN122) is registered as the live production subnet at netuid 122. 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 122 Identifies the Subnet On-Chain
Bittensor assigns every subnet a unique numeric identifier called a netuid, and Subnet 122 is the subnet registered at netuid 122 (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 CookingTAO from every other subnet.
For a reader, this means “Subnet 122” and “netuid 122” refer to the same on-chain slot. A claim about CookingTAO 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 122 CookingTAO should not be read as generic Bittensor subnet documentation, mining-profitability or investment advice, or a guarantee of mining returns. It names one subnet whose on-chain identity is registered with the description “Democratizing Bittensor Mining” on netuid 122 (Understanding Subnets, Glossary: Netuid).