Subnets
- Indexed
- 129
- Probed healthy
- Loading Probed healthy
Directory. Search and compare every subnet.
Rankings. The subnets that carry the network.
30d · ranked by share of daily emission, changed over the window · chain-direct
Revenue evidence. Which subnets have readable external revenue, not a speculative ranking.
- Readable revenue
- Loading Readable revenue
- Evidence coverage
- Loading Evidence coverage
1d · source-linked external revenue coverage
Domains. What the network is building.
- Loading Emission share by capability domain legend
loading capability-domain coverage
Churn. Subnets registering and deregistering, by day.
- Loading The ten most recent lifecycle transitions
registration and deregistration history · chain-direct
Subnet registry API and artifacts
- subnets/movers
https://api.metagraph.sh/api/v1/subnets/movers- chain/subnet-lifecycle
https://api.metagraph.sh/api/v1/chain/subnet-lifecycle- agent-catalog
https://api.metagraph.sh/api/v1/agent-catalog- revenue coverage
https://api.metagraph.sh/api/v1/chain/revenue-coverage- subnets.json artifact
https://api.metagraph.sh/metagraph/subnets.json
What a subnet is
A subnet is a self-contained incentive mechanism running on the Bittensor chain. Miners produce work, validators score it, and emission is distributed by the resulting consensus. The netuid identifies the slot, not the project: slots are competitive, so the team occupying netuid 38 today may not be the one occupying it next quarter. That is why every record here is dated.
How the health figures are produced
Every registered surface is probed on a 15-minute cycle and the outcome is recorded as-is. Uptime, latency and incident history are derived from those probes alone — no operator can set them, and neither can we. A subnet with no public interface is shown as having none rather than being quietly omitted.