Features

A complete master stack for multi-challenge subnets.

The product surface mirrors the new Platform code: registry administration, public challenge proxying, Docker orchestration, GPU server tracking, fallback weights, and Bittensor weight submission.

Master API

One registry for many challenges

Platform runs a private FastAPI master that manages challenge records, lifecycle status, Docker image metadata, emission percent, runtime resources, volumes, environment, and admin-safe token hints.

registry, status, resources, admin API

Challenge Runtime

Independent containers per challenge

Each challenge can live in its own repository, publish a GHCR image, mount persistent SQLite state, and expose the standard internal get_weights contract consumed by the master.

Docker images, SQLite volumes, get_weights

Public Proxy

Eligible challenges get public routes

The proxy forwards safe requests to eligible challenge containers, strips sensitive headers, blocks private paths, and returns upstream responses through /challenges/{slug}.

proxy routes, lifecycle status, safe forwarding

Weight Aggregation

Challenge weights become subnet weights

The master collects hotkey weights from each active challenge, normalizes challenge emissions, maps hotkeys to UIDs, and submits the final weight vector to Bittensor.

hotkeys → UIDs → set_weights

01

Challenge lifecycle

Admins define challenge records and move them through draft, active, inactive, or disabled states.

Registry records
GHCR images
Emission percent
Public proxy path

02

Validator operations

Validators run the master, pull challenge containers, inspect status, and collect active challenge weights.

Runtime operations
Container groups
GPU server health
Fallback weights

03

Challenge experience

Users can browse challenge status, inspect PRISM architecture submissions, and understand how each track maps into registry-backed Platform operations.

Challenge rows
Registry metadata
Architecture dossiers
Weight flow