Skip to main content
BASE is a multi-challenge Bittensor subnet. It runs independent challenges under one validator network, routes your traffic to the right challenge, collects raw challenge weights, normalizes emissions, maps your hotkey to a Bittensor UID, and publishes the final vector that validators submit on-chain (docs/miner/README.md:1-8, README.md:21-31). As a miner you do not build against subnet-wide scoring logic. You pick a challenge, follow that challenge’s submission contract, and use the subnet’s public proxy to reach the challenge (docs/miner/README.md:3-8).

​
The miner flow

The end-to-end flow is fixed (docs/miner/README.md:9-18):
1

Choose a challenge

Pick the challenge you want to compete in and read its repository and miner guide.
2

Build the artifact

Build the submission artifact in the format that challenge requires.
3

Submit through the proxy

Submit through the challenge’s public route, exposed by the subnet proxy.
4

Track status and leaderboards

Track challenge-specific status, reports, and leaderboards.
5

Earn weight

Earn rewards when the challenge exports a raw weight for your hotkey and the subnet normalizes it into final weights.

​
How your traffic is routed

Every challenge has a slug, such as agent-challenge, data-fabrication, bounty-challenge, or prism. The proxy uses that slug to route public challenge requests to the correct isolated challenge service (docs/miner/README.md:20-34): 
POST /challenges/{challenge_slug}/...
GET  /challenges/{challenge_slug}/...
The path after the slug belongs to the challenge repository. The subnet does not define the artifact format, task rules, scoring rubric, or leaderboard fields for any challenge (docs/miner/README.md:33-34).

​
What the subnet does for you

The subnet provides (docs/miner/README.md:114-123):
  • one public entry point for multiple challenges;
  • challenge routing by slug;
  • central challenge discovery;
  • final normalization across challenge emissions;
  • hotkey-to-UID mapping;
  • final on-chain weight submission.

​
What each challenge defines

Each challenge owns its own contract (docs/miner/README.md:125-135):
  • accepted submission format;
  • authentication and signature rules;
  • task or project requirements;
  • scoring algorithm;
  • evaluation limits;
  • leaderboard output;
  • public status and result endpoints.

​
How rewards work

Challenge scores are not submitted directly to Bittensor. The flow is (docs/miner/README.md:137-149):
  1. The challenge evaluates your work.
  2. The challenge exports raw hotkey weights.
  3. The subnet applies that challenge’s configured emission share.
  4. The subnet normalizes across all active challenge outputs.
  5. The subnet maps hotkeys to Bittensor UIDs.
  6. Validators submit the final weights on-chain.
A strong score in one challenge contributes according to that challenge’s configured emission share. The two primary challenges weight at PRISM 30 and agent-challenge 15 emission percent (src/platform_network/cli_app/main.py:292-293).

​
Miner checklist

Before you submit (docs/miner/README.md:151-161):
  • Confirm the challenge slug and repository.
  • Read the challenge miner guide.
  • Use the challenge’s required artifact format.
  • Sign your requests with your hotkey.
  • Monitor the challenge leaderboard, not only the subnet layer.
  • Keep your hotkey consistent across submissions.
  • Do not assume two challenges share the same scoring rules.
The subnet runs on netuid 100 (src/platform_network/config/settings.py:12). Your hotkey must be registered on netuid 100 before a signed submission is accepted; see Wallet & registration.

​
Next steps

Miner quickstart

Go from zero to a signed submission.

Install the miner

Set up the tooling and wallet.

Choosing a challenge

Compare agent-challenge and PRISM.

Submitting your work

Learn the upload protocol.