> ## 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.

# Challenges explained

> A challenge is an independent competition plugged into BASE. Miners follow challenge docs; the subnet only coordinates weights.

A **[challenge](/concepts/glossary#challenge)** is where work happens on BASE. The subnet is the coordination layer. Each challenge defines a competition with its own rules.

## What a challenge is

A challenge is an independent repository and Docker image. It owns logic, public routes, submissions, scoring data, database schema, and challenge-local files. State lives on the challenge's own data volume, separate from the subnet control plane.

Standard internal contract:

```text theme={"dark"}
GET /health
GET /version
GET /internal/v1/get_weights
```

`get_weights` is how BASE reads raw hotkey weights. It is token-authenticated and not exposed on the public proxy.

## Primary challenges

<Tabs>
  <Tab title="Agent Challenge">
    Software-engineering agents. Production scoring is miner self-deploy on Phala Intel TDX with attested review, RA-TLS golden key release, and Terminal-Bench eval from a baked guest cache. No Base LLM gateway on the scored path.

    [Agent Challenge miner pack →](/challenges/agent-challenge)
  </Tab>

  <Tab title="PRISM">
    Learn-from-scratch neural architecture search. Miners submit two scripts; the challenge re-executes training and computes prequential bits-per-byte.

    [PRISM miner pack →](/challenges/prism/overview)
  </Tab>
</Tabs>

## Additional challenges

<Accordion title="Bounty Challenge">
  Owner-reviewed project bounties that need human judgment. [Guide →](/challenges/bounty-challenge)
</Accordion>

<Accordion title="Data Fabrication">
  Dataset-generation harnesses for agentic coding conversations. [Guide →](/challenges/data-fabrication)
</Accordion>

<Accordion title="Agent SWE">
  Real repositories as fail-to-pass agent benchmarks. [Guide →](/challenges/agent-swe)
</Accordion>

## How a challenge plugs in

BASE routes public requests by slug, reads protected `get_weights`, and normalizes scores. Everything else is challenge-owned.

<CardGroup cols={2}>
  <Card title="Challenges tab" icon="trophy" href="/challenges/overview">
    Full catalog and miner packs.
  </Card>

  <Card title="How the subnet works" icon="diagram-project" href="/concepts/how-it-works">
    End-to-end flow.
  </Card>
</CardGroup>