Part of #427.
Subnet 6 — Numinous is missing from the registry: public data artifact, SSE stream. Research whether the subnet exposes these, find the real public link(s), and submit them.
Find it
Search for the subnet's official public data artifact, SSE stream (project site / GitHub / docs / Bittensor). Confirm each link is real, public, no-auth, and genuinely SN6's — cross-reference the subnet name + Bittensor. ⚠️ Many subnets simply don't expose a public API yet, and on-chain identity links are often stale/dead — verify each link actually resolves before submitting. If the subnet genuinely exposes no such public surface, comment here so a maintainer can close it.
Submit — one candidate per surface, one file
First find the provider slug for the team/operator behind the surface (a wrong slug is the #1 validation failure): npm run providers:list. Then generate one candidate file:
npm run candidate:new -- --netuid 6 --kind data-artifact \
--url <real-public-url> --source-url <link-that-proves-it> \
--provider <slug> --submitted-by <your-login> --write
Open a PR touching exactly one registry/candidates/community/*.json file — the review gate validates + reviews it.
Rules: a real url that resolves · a source_url that proves it's official · one file · no generated artifacts · public_safe: true · auth_required: false. Full guide: CONTRIBUTING → Community submissions.
Part of #427.
Subnet 6 — Numinous is missing from the registry: public data artifact, SSE stream. Research whether the subnet exposes these, find the real public link(s), and submit them.
Find it
Search for the subnet's official public data artifact, SSE stream (project site / GitHub / docs / Bittensor). Confirm each link is real, public, no-auth, and genuinely SN6's — cross-reference the subnet name + Bittensor.⚠️ Many subnets simply don't expose a public API yet, and on-chain identity links are often stale/dead — verify each link actually resolves before submitting. If the subnet genuinely exposes no such public surface, comment here so a maintainer can close it.
Submit — one candidate per surface, one file
First find the provider slug for the team/operator behind the surface (a wrong slug is the #1 validation failure):
npm run providers:list. Then generate one candidate file:Open a PR touching exactly one
registry/candidates/community/*.jsonfile — the review gate validates + reviews it.Rules: a real
urlthat resolves · asource_urlthat proves it's official · one file · no generated artifacts ·public_safe: true·auth_required: false. Full guide: CONTRIBUTING → Community submissions.