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

Platform

Master validator, registry, proxy, runtime, and weights.

PlatformPlatform

Configuration

YAML and environment settings for master, validator, database, Docker, GPU, weights, security, and observability.

#platform/configuration
platformconfigyamlenvironment

Sources

SettingsMaster configValidator config

Settings groups

Platform loads structured settings and supports environment overrides for deployment.

GroupCommon keys
networkname, netuid, chain endpoint, wallet, hotkey, master UID.
masteradmin/proxy hosts and ports, registry state file, epoch interval.
validatorregistry URL and retry interval.
databasePostgreSQL URL and migration settings.
dockernetwork, secret directory, broker URL, allowed images.
weightsfallback URL/token, signing secret, latest weights file.
securityadmin token or token file.
observabilityJSON logs, Sentry DSN, OpenTelemetry service name.

Secrets

Production deployments should prefer file-backed secrets. Challenge tokens, admin tokens, signing keys, and GPU-agent tokens should never be exposed through registry responses or public logs.