Compute subnets
Compute on Bittensor today
9 subnets are classified under compute. 8 publish at least one first-party interface and 9 have a surface that answered our most recent probe. These are the subnets where an endpoint being reachable matters most, because you are buying availability. Probe history is the honest signal: a broker that answers consistently is worth more than one advertising a larger fleet it cannot keep online.
| Subnet | Readiness | Surfaces | Health |
|---|---|---|---|
| SN12 Compute Horde | 100 | 2/14 | |
| SN51 lium.io | 100 | 8/161 | |
| SN64 Chutes | 96 | 19/76 | |
| SN106 Nodexo | 86 | 4/15 | |
| SN25 Mainframe | 83 | 1/12 | |
| SN128 ByteLeap | 83 | 2/10 | |
| SN48 Quantum Compute | 81 | 2/9 | |
| SN27 Orion | 78 | 0/11 | |
| SN39 Basilica | 72 | 1/12 |
What "compute" means here
Subnets renting or brokering machine time — GPUs, containers, verifiable execution — where the product is capacity rather than a model's output.
How the classification is derived
Categories come from what a subnet publishes about itself — its declared purpose, its source repository and the interfaces it exposes — not from a hand-maintained list. A subnet can belong to several, and 60 of 129 currently belong to none, which is a coverage gap in our data rather than a statement about those subnets.