Platformnetwork
Challenges

Documentation

Complete docs for every challenge

Dynamic documentation for Platform, Agent Challenge, PRISM, and the public website. Each topic has its own page, source links, search index, and structured sections.

Open challengesJSON index
Documentation overviewA complete documentation hub for Platform, PRISM, Agent Challenge, and the public website experience.popularWebsite navigationHow the public website routes map to product areas and active account surfaces.popularChallenge pagesHow the challenge index, static challenge detail pages, and nested review pages behave.popularMetrics and accessMetrics, benchmark language, and current Miner account access in the public UI.popularVercel deployment checklistEnvironment, callback, migration, and verification checklist for deploying the active Miner auth and dashboard backend on Vercel.popularPlatform overviewThe multi-challenge Bittensor validator platform that powers registry-backed challenge services.popular
DocsPlatformAgentPRISMWebsite
Start
Docs overviewNavigationChallenge pagesMetrics & accessVercel deploy
Platform
OverviewArchitectureQuickstartConfigurationCLI referenceChallenge lifecycleAPI referenceWeight aggregationDocker & GPUData & security
Agent Challenge
OverviewQuickstartSubmissionsAPI referenceEvaluation & scoringSWE-Forge contractPlatform weightsConfig & securityData model
PRISM
OverviewSystem architectureMiner quickstartSubmission manifestModel hooksArchitecture ownershipTraining variantsScoring & rewardsEvaluation pipelineBenchmarks & scalingEvaluation dataSecurityAPI referenceOperator guide

PRISM

Architecture mining, training variants, scoring, and operators.

PRISMPRISM

PRISM operator guide

Register PRISM, run workers, assign validators, collect weights, and diagnose failures.

#prism/operator-guide
prismoperatorvalidatortroubleshooting

Sources

Platform challenge schemaPlatform weight service

Operator checklist

Treat PRISM as a normal Platform challenge with additional GPU worker and hidden-data requirements.

  • Register the `prism` challenge with image, version, emission percent, resources, volumes, env, and required capabilities.
  • Activate only after health checks, token mounting, and worker queues are verified.
  • Confirm public proxy paths serve only safe public routes.
  • Confirm `/internal/v1/get_weights` is reachable from the Platform master.
  • Monitor backlog, GPU utilization, failed builds, score deltas, fallback weights, and final UID submission.

Troubleshooting

Most PRISM incidents fall into schema, artifact, runtime, evaluation, or weight-publication failures.

SymptomLikely cause
Submission stuck validatingManifest schema or checksum failure.
Build passes locally but fails on validatorsUndeclared dependency, network assumption, or hardware mismatch.
No leaderboard movementQueue backlog or consensus not reached.
Weights emptyToken failure or no positive hotkey weights.
Public route exposes internal dataProxy/service mount misconfiguration.