> ## Documentation Index
> Fetch the complete documentation index at: https://docs.joinbase.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# What is BASE?

> BASE is the multi-challenge Bittensor subnet on netuid 100: validator infrastructure plus pluggable challenges.

BASE is a **multi-challenge [Bittensor](https://bittensor.com/) [subnet](/concepts/glossary#subnet)**. It lets independent challenges run under one validator network, routes miner traffic to the right challenge, collects raw weights, normalizes [emissions](/concepts/glossary#emissions), maps miner [hotkeys](/concepts/glossary#hotkey) to [UIDs](/concepts/glossary#uid), and publishes the final vector for [validators](/concepts/glossary#validator) to submit on-chain.

## Role split (product truth)

| Role                    | What they do                                                                                                      |
| ----------------------- | ----------------------------------------------------------------------------------------------------------------- |
| **BASE validators**     | Run subnet infrastructure: master, proxy, weight setting, submitter, wallet as validator                          |
| **Miners**              | Compete **inside challenges**; each challenge owns submit path, eval, costs, TEE                                  |
| **Challenge operators** | Run or configure a challenge service (allowlists, datasets, key release). Not the same as the BASE validator mint |
| **Challenge authors**   | Ship new challenge repos using the create/SDK guides                                                              |

Miners do not "mine Base generic." Validators do not complete Agent Challenge TEE self-deploy for miners as the production score path.

## The subnet, in one picture

* **Challenges** define the work. Each lives in its own repository and owns submissions, scoring, and miner experience.
* **Miners** pick a challenge and follow that challenge.
* **Validators** keep the network weight vector honest on-chain.

## netuid 100

BASE runs on **netuid 100**. Configure wallets, submitters, and validators against that netuid.

## What the subnet does

* Tracks active challenges and emission shares
* Routes `/challenges/{slug}/...`
* Isolates challenge failure from the rest of the network
* Normalizes challenge outputs, maps hotkeys to UIDs
* Supports on-chain submit of the final vector

## Where to go next

<CardGroup cols={2}>
  <Card title="How the subnet works" icon="diagram-project" href="/concepts/how-it-works">
    Submission to on-chain weights.
  </Card>

  <Card title="Miners and validators" icon="users" href="/concepts/miners-and-validators">
    Role boundaries without mixed messaging.
  </Card>

  <Card title="Challenges" icon="trophy" href="/challenges/overview">
    Miner home and challenge catalog.
  </Card>

  <Card title="Validators" icon="shield-halved" href="/validators/overview">
    BASE operator path.
  </Card>
</CardGroup>