Skip to main content
RegistrySubnets / 000

root

Τrootbaseline-augmentedchain-rpcrootsystem

Manual root/system overlay for Bittensor base-layer surfaces. Subtensor RPC endpoints are chain-level infrastructure, not subnet application APIs.

WebsiteDocsRepoDashboard
Netuid
000
Native chain id
updated 1h ago
Participants
64
Active UIDs
updated 1h ago · weekly window
Endpoints
17
tracked
updated 1h ago
Surfaces
17
7 kinds supported
updated 1h ago
Uptime
—
current window
updated 1h ago · 90d window
Latency p50
—
median probe latency
updated 1h ago · 90d window
Completeness
100%
maintainer-reviewed
registry profile
updated 1h ago
Evidence
4
primary sources
updated 1h ago
Integration readiness
22/ 100Identity only
Unknown
Start here: Bittensor website · opentensor
Callable APICallable nowDocumentedAuth clarityProfile completeActive
3 operational interfaces · missing openapi, subnet-api, sse, data-artifact

Public resources

Endpoints, curated surfaces, and tracked schemas for this subnet.

Subnet profile

Chain identity, AMM economics, ownership keys, and registry curation.

Tempo
100
Type
root
Reg. block
—
Mechanisms
1
Ownership
No ownership keys recorded.
Registry curationReviewed
Completeness100%
probedmaintainer-reviewedconf · highreviewed

Economics

On-chain emission share, stake, validators, and market data.

Loading economics…

Network history

Daily on-chain neuron/validator counts, total stake, and emission over time.

Reliability

Per-surface uptime SLA and latency percentiles (p50/p95/p99) over 7d/30d.

Per-surface reliability · uptime · latency percentiles
Loading reliability…

Sources & evidence

Primary links and recorded evidence backing this profile.

Incident history

Recorded health regressions and SLA breaks for this subnet.

Known gaps

Missing resources, profile incompleteness, and curation notes.

Missing kinds
openapisubnet-apissedata-artifact
  • · Root/system is not expected to expose subnet-specific SSE or data artifacts.
  • · Commercial RPC providers with API-key-gated endpoints are tracked as providers, not public probeable surfaces.
Help close these gaps by opening a PR against the public registry repo.