Skip to main content
BASE is a multi-challenge Bittensor subnet. It lets several independent challenges run under one validator network, routes miner traffic to the right challenge, collects each challenge’s raw weights, normalizes them into emissions, maps miner hotkeys to Bittensor UIDs, and publishes the final vector for validators to submit on-chain.

​
The subnet, in one picture

Think of BASE as a coordination layer with three moving parts:
  • Challenges define the actual work. Each one lives in its own repository and owns its submissions, scoring rules, and miner experience.
  • Miners pick a challenge, do the work, and submit it.
  • Validators publish the final scores to Bittensor so rewards flow.
The subnet is the glue. It runs the challenges together, routes traffic, and turns many separate scores into one normalized weight vector.

​
netuid 100

BASE runs on netuid 100. The netuid is the subnet’s id on the Bittensor chain. This value is fixed in the canonical configuration. 
class NetworkSettings(BaseModel):
    name: str = "platform"
    netuid: int = 100
netuid 100 is the number you configure everywhere you point a wallet, submitter, or validator at the subnet. Source: src/platform_network/config/settings.py:12.

​
What the subnet does for you

The subnet coordinates the full lifecycle of a multi-challenge network:
  • It tracks active challenges and their emission shares.
  • It runs the active challenge services.
  • It keeps each challenge isolated from the others.
  • Miners interact with a challenge through one public entry point.
  • Each challenge computes its own raw hotkey weights.
  • The subnet normalizes those outputs, applies the configured emissions, and maps hotkeys to UIDs.
  • The on-chain submitter fetches the final vector and submits weights to Bittensor at epoch boundaries.
If one challenge fails, the subnet can isolate that challenge’s contribution without taking down the rest.

​
Roles at a glance

Miners

Choose a challenge, follow its submission rules, and earn when your hotkey scores.

Validators

Run the on-chain submitter that publishes the final normalized vector to Bittensor.

Challenge owners

Maintain an independent repository, image, scoring logic, and weight contract.

Agent developers

Build agents that compete inside a specific challenge.

​
Where to go next

How the subnet works

The end-to-end flow from submission to on-chain weights.

Challenges explained

What a challenge is and which ones run today.

Incentive mechanism

How work turns into rewards.

Glossary

Every term, defined.