Subnet 111: Claims
Claims is Bittensor Subnet 111. Its on-chain identity registers the subnet for turning scientific literature into a structured claim-evidence graph.
What Claims Provides
The registered identity describes Claims as a subnet “turning scientific literature into a structured claim-evidence graph.” Miners produce that structured output, and the network rewards the strongest results. The codebase is the oneoneone-io/subnet-111 repository, whose public README currently describes a different oneoneone user-generated-content platform.
Public Source Divergence
The public sources for Subnet 111 do not use identical descriptions. The live on-chain identity for netuid 111 names the subnet Claims and describes it as turning scientific literature into a structured claim-evidence graph.
The linked oneoneone repository README uses different product language. It describes oneoneone as a decentralized protocol for accessing user-generated content, with miners collecting and formatting content from public platforms and validators checking data quality. The public oneoneone website also uses the oneoneone brand for the platform associated with the project.
Because those source descriptions diverge, the live identity verifies the Claims name and claim-evidence graph description, while the repository and website verify the oneoneone user-generated-content platform description. The available sources do not, by themselves, prove that the two descriptions are equivalent statements of the same current subnet task.
Repository-Described Flow
Under the repository description, the subnet is organized around content collection, validation, and access. The README lists miners, validators, and API consumers as participant groups. Miners collect and format public user-generated content. Validators assess the quality of returned data. API consumers access the structured content through the oneoneone platform.
That flow makes the repository-described task a content-access task rather than a model-hosting task. The work product is structured external content that can be checked and served to downstream users. The README also describes analysis around authenticity, intent, sentiment, and translation, which explains why quality checks matter alongside collection coverage.
At the incentive level, the repository framing ties miner value to usable returned data and validator value to judging that data. Those validator judgments become the weights that flow through Yuma Consensus.
Miner and Validator Roles
Subnet 111 operates under the standard Bittensor two-role structure. The live identity frames the subnet around claim-evidence extraction from scientific literature. The repository frames the system around user-generated-content collection and validation. In either framing, validators evaluate the work submitted by miners and set weights. Reward distribution follows Yuma Consensus.
On-Chain Identity
The live Finney identity for netuid 111 registers the subnet name as Claims, with the description “Turning scientific literature into a structured claim-evidence graph.” The GitHub repository is oneoneone-io/subnet-111; no project website URL or Discord is set in the identity. Live subnet data is available on TaoStats.
Relationship to Yuma Consensus
Subnet 111 uses Yuma Consensus to convert the content-quality weight vectors that validators submit 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.
In Claims’s context, validators evaluate the structured content or claim-evidence output submitted by miners and use those quality assessments to set weight vectors for the subnet. The Emission documentation describes how those 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 Claims (SN111), that sequence changes how readers should interpret claim-evidence extraction examples and content-quality scoring outcomes.
In localnet, Claims-compatible miners and validators can be developed and tested in an isolated environment. Localnet extraction results and emission outcomes do not represent production subnet performance.
On testnet, Claims-compatible content collection and validation workflows can be exercised in a shared, non-production network. Testnet data quality scores and validator weights are separate from mainnet subnet state.
On mainnet, Claims (SN111) is the live production subnet where miners extract and structure content and validators evaluate data quality to determine real Bittensor emissions. The Claims repository describes the mechanism that applies on the production network.
The Bittensor Networks reference separates mainnet, testnet, and localnet. A content extraction result or emission outcome from one environment should not be read as representing production subnet performance in another environment.
Netuid 111 Identifies the Subnet On-Chain
Bittensor assigns every subnet a unique numeric identifier called a netuid, and Subnet 111 is the subnet registered at netuid 111 (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 Claims from every other subnet.
For a reader, this means “Subnet 111” and “netuid 111” refer to the same on-chain slot. A claim about Claims 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 111 Claims should not be read as generic Bittensor subnet documentation, a peer-reviewed scientific authority, or proof that any extracted claim is true. It names one subnet whose on-chain identity registers it for turning scientific literature into a structured claim-evidence graph on netuid 111 (Understanding Subnets, Glossary: Netuid).