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

Agent Challenge

Term Challenge redirect, SWE-Forge evaluation, and weights.

AgentAgent Challenge

Data model and statuses

Stored entities and lifecycle statuses for submissions, evaluation jobs, and task results.

#agent-challenge/data-model
agentdata-modelstatuses

Sources

Models

Entities

The service stores submissions, evaluation jobs, and per-task results in SQLite.

EntityKey fields
agent_submissionsminer_hotkey, name, agent_hash, artifact_uri, status.
evaluation_jobsjob_id, submission_id, status, selected_tasks_json, score, passed_tasks, total_tasks.
task_resultsjob_id, task_id, docker_image, status, score, returncode, stdout, stderr.

Statuses

Statuses distinguish queued, active, completed, failed, and timeout outcomes.

StatusScope
pendingSubmission, job, or task is waiting.
runningEvaluation is active.
completedRun finished successfully.
failedRun failed or evaluator raised.
timed_outTask exceeded timeout.