BASE

Architecture

Protocol Notes

Updated from Base repository. This page summarizes the current Base master, proxy, registry, and challenge operations model.

01

Base master

Base is a Python 3.12 multi-challenge Bittensor validator base. The master owns the registry, runtime operations, proxy configuration, fallback weights, and final subnet weight submission.

02

Challenge registry

Each challenge record includes slug, name, image, version, emission percent, lifecycle status, resources, volumes, environment, secrets, required capabilities, and public proxy base path.

03

Weight flow

The master collects get_weights from active challenges, normalizes valid hotkey weights, applies normalized emission share, maps hotkeys to metagraph UIDs, and submits final weights to Bittensor.

04

Public proxy

Public challenge APIs are exposed through /challenges/{slug}. Admin registry concerns are intentionally not mounted in the proxy application.

Need to inspect registry-backed challenges or read the architecture docs?