Subnet 95: Actual
Actual is Bittensor Subnet 95.
What Actual Provides
The on-chain description registers Subnet 95 as a “Heterogeneous inference network by Actual Computer Inc.” The registered project website is actual.inc. Public technical documentation for the specific subnet mechanism is not available through the on-chain identity alone, as the registered GitHub repository is not publicly accessible at this time.
Miner and Validator Roles
Subnet 95 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 live Finney identity for netuid 95 registers the subnet name as Actual and the description as “Heterogeneous inference network by Actual Computer Inc.” The registered project site is actual.inc. The registered GitHub field points to github.com/actual-computer/actual-subnet-95, though that repository is not publicly accessible. The Discord field is blank. Live subnet data is available on TaoStats.
Relationship to Yuma Consensus
Subnet 95 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 the registered GitHub repository for Subnet 95 is not publicly accessible, no source-backed description of how validators score miners or what weight vectors represent is available. The Emission documentation describes how consensus weights determine each participant’s share of the subnet’s accumulated emission each tempo, and those mechanics apply to Subnet 95 through the standard Bittensor incentive layer.
Development Stage Context
The Introduction to Bittensor describes subnet development as moving from localnet to testnet and then mainnet. For Actual (SN95), 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, Actual (SN95) is registered as the live production subnet at netuid 95. 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 95 Identifies the Subnet On-Chain
Bittensor assigns every subnet a unique numeric identifier called a netuid, and Subnet 95 is the subnet registered at netuid 95 (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 Actual from every other subnet.
For a reader, this means “Subnet 95” and “netuid 95” refer to the same on-chain slot. A claim about Actual 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 95 Actual should not be read as generic Bittensor subnet documentation, an endorsement of the operator Actual Computer Inc., or proof that any single inference response is correct. It names one subnet’s heterogeneous inference network operated by Actual Computer Inc. on netuid 95 (Understanding Subnets, Glossary: Netuid).