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

Platform architecture

How the master, proxy, registry, Docker runtime, challenges, and Bittensor weight loop fit together.

#platform/architecture
platformarchitecturedockerproxyweights

Sources

Architecture docMaster serviceProxy appDocker orchestrator

Main components

The control plane is split into private APIs, public proxy traffic, runtime orchestration, and Bittensor integration.

ComponentPurpose
Admin APIPrivate challenge registry and lifecycle operations.
Public proxyForwards safe public traffic to active challenge containers.
Docker orchestratorPulls images, starts containers, mounts volumes and secrets, verifies readiness.
Docker brokerRuns bounded challenge-side Docker jobs without exposing the host socket to challenges.
Weight serviceCollects per-challenge weights and submits normalized UID weights.

Runtime flow

A challenge becomes public only after it is registered, activated, pulled, started, and validated through health/version checks.

The proxy accepts `/challenges/{slug}/...` only for active challenges and blocks internal paths from public access.