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

Weight aggregation

How challenge scores become final Bittensor UID weights.

#platform/weight-aggregation
platformweightsbittensoremissions

Sources

AggregatorChallenge clientWeight service

Epoch flow

For each epoch, the master lists active challenges, maps hotkeys to UIDs, calls every challenge internal `get_weights` route, normalizes per-challenge weights, applies emission shares, and submits final UID weights.

Normalization rules

The aggregator intentionally cleans challenge output before it can affect subnet weights.

  • Ignore non-finite, zero, and negative raw weights.
  • Normalize successful weights inside each challenge.
  • Normalize emission_percent across successful challenge results.
  • Drop unknown hotkeys that cannot be mapped to metagraph UIDs.
  • Normalize final UID weights before submission.