Dosu Logo
Ask
Documents
all-subnet-registry
all-subnet-registry
Type
External
Status
Published
Created
Jun 6, 2026
Updated
Jun 6, 2026
Updated by
Dosu Bot
Source
View

All-Subnet Registry Model#

Metagraphed covers every active Finney subnet through chain-native data plus curated public-interface overlays.

Current Coverage#

  • 129 active Finney netuids.
  • 1 root/system entry at netuid 0.
  • 128 application subnets.
  • 129 curated overlays.
  • 0 native-only entries.
  • Allways SN7 and Gittensor SN74 are adapter-backed.
  • Root netuid 0 carries Bittensor base-layer Subtensor RPC/WSS surfaces.

Native Snapshot#

registry/native/finney-subnets.json is generated from decoded Bittensor SDK data.

It is canonical for:

  • active netuid existence;
  • root/system versus application subnet classification;
  • raw chain subnet name, symbol, and name-quality classification;
  • participant count;
  • tempo;
  • registration block;
  • mechanism count;
  • capture block and source metadata.

It is not the place for docs URLs, dashboards, public APIs, or probe rules.

Native subnet names can degrade to placeholders such as unknown when the upstream chain/RPC source cannot provide a meaningful label. In that case, public registry artifacts preserve the raw native value through native_name and native_name_quality, while builder-facing name stays sourced from the reviewed overlay when available.

Curated Overlays#

registry/subnets/*.json and registry/subnets/generated/*.json contain curated interface metadata.

Overlays are canonical for:

  • public APIs;
  • OpenAPI/Swagger surfaces;
  • SSE/event streams;
  • dashboards;
  • docs;
  • repositories;
  • data artifacts;
  • Subtensor RPC/WSS endpoints on root/system;
  • read-only probe rules.

An overlay must reference a netuid that exists in the native snapshot unless it is explicitly marked pending.

Curation levels:

  • native: chain-derived only;
  • candidate-discovered: public candidates exist but are not verified;
  • machine-verified: safe public probes verified promoted surfaces;
  • maintainer-reviewed: a human reviewed the overlay;
  • adapter-backed: subnet-specific public data dimensions are modeled.

Candidate Queue#

registry/candidates is for unverified public interface candidates from community submissions or third-party discovery.

Candidates are never treated as verified surfaces. They must pass verification and maintainer review before being treated as reviewed registry truth.

npm run discover:candidates generates a public-source candidate bundle from enrichment sources such as TaoMarketCap, Tensorplex subnet-docs, Taopedia articles, GitHub README links, and public websites.

npm run verify:candidates writes registry/verification/latest.json with live, redirected, auth-required, dead, unsafe, unsupported, rate-limited, transient, timeout, or content-mismatch classifications.

npm run curate:baseline promotes only live/redirected public-safe candidates into generated baseline overlays. It does not overwrite hand-curated overlays.

Review Workflow#

registry/reviews/maintainer-reviewed.json stores public-safe maintainer decisions.

npm run review:promote applies those decisions to overlays. Review data is limited to netuid, slug, decision, reviewed timestamp, confidence, public source URLs, and notes.

Generated artifacts expose review state through:

  • /metagraph/review/curation.json
  • /metagraph/review/gap-priorities.json
  • /metagraph/review/adapter-candidates.json
  • /metagraph/review/maintainer-decisions.json

Generated Artifacts#

public/metagraph/subnets.json lists every active chain subnet.

public/metagraph/surfaces.json lists only curated/verified public interface surfaces.

public/metagraph/rpc-endpoints.json lists Bittensor base-layer RPC/WSS endpoints and live probe metadata.

public/metagraph/rpc/pools.json scores RPC/WSS endpoints for future read-only endpoint routing.

public/metagraph/coverage.json summarizes chain coverage, curated overlays, native-only stubs, probed subnets, surfaces, and candidate counts.

public/metagraph/candidates.json lists unverified candidate surfaces with source provenance.

public/metagraph/review-queue.json lists candidate surfaces that need maintainer review.

public/metagraph/curation.json lists curation level, review state, source count, and gaps for every active subnet.

public/metagraph/gaps.json lists missing docs/repo/site/dashboard/API/OpenAPI/SSE/data-artifact facets by subnet.

public/metagraph/verification/latest.json exposes the latest candidate verification snapshot.

public/metagraph/subnets/{netuid}.json exposes per-subnet static detail artifacts for app and API consumers.

public/metagraph/health/* exposes surface health, per-subnet health, history, and badge-input data under metagraph.sh.

public/metagraph/adapters/* exposes safe subnet-specific public metrics for adapter-backed pilots.

public/metagraph/search.json exposes a compact search index for subnets, surfaces, and providers.

public/metagraph/freshness.json, source-health.json, source-snapshots.json, changelog.json, and evidence-ledger.json expose backend freshness, upstream source health, source-input hashes, generated change summaries, and public evidence records.

public/metagraph/r2-manifest.json lists artifacts intended for versioned R2 history upload.

Worker API routes under /api/v1/* wrap these artifacts without replacing them as canonical truth. The Worker reads static assets first, can fall back to R2, and can use an optional KV latest pointer when configured.