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

# Choosing a challenge

> Compare Agent Challenge, PRISM, and secondary challenges. Each owns its full miner path.

You compete in **one challenge at a time** by following that challenge's docs. BASE only routes traffic, discovers challenges, and normalizes weights. Artifact formats and scoring never share a single Base-global path.

## Primary challenges

<CardGroup cols={2}>
  <Card title="Agent Challenge" icon="terminal" href="/challenges/agent-challenge">
    Build a software-engineering agent. Production: miner-funded Phala CPU TDX review then eval, RA-TLS golden key, Terminal-Bench from a baked guest cache. Slug `agent-challenge`.
  </Card>

  <Card title="PRISM" icon="microscope" href="/challenges/prism/overview">
    Submit `architecture.py` + `training.py`. Challenge re-executes train under forced init and scores prequential bits-per-byte. Slug `prism`.
  </Card>
</CardGroup>

### Agent Challenge (summary)

* **Artifact:** agent ZIP, root `agent.py` with `class Agent` (build from `baseagent`)
* **After upload:** self-deploy measured review CVM, then after verified allow, eval CVM
* **Costs:** Phala CVM spend capped on the self-deploy path (default hard joint cap \$20); OpenRouter for review under measured `.rules`
* **Not:** Base LLM gateway on the scored path; validator-deployed score jobs for miners

Full pack: [Agent Challenge](/challenges/agent-challenge).

### PRISM (summary)

* **Artifact:** two distinct scripts in a zip (or directory snapshot)
* **Flow:** AST sandbox → LLM hard gate → GPU re-execution → challenge-authored score
* **Anti-cheat:** forced random init, no network in container, secret held-out splits, miner-reported metrics ignored

Full pack: [PRISM](/challenges/prism/overview).

## Secondary challenges

| Challenge        | Slug (typical)     | Miner angle                   | Guide                                 |
| ---------------- | ------------------ | ----------------------------- | ------------------------------------- |
| Bounty           | `bounty-challenge` | Owner-reviewed finished work  | [Guide](/challenges/bounty-challenge) |
| Data Fabrication | `data-fabrication` | Dataset harness quality       | [Guide](/challenges/data-fabrication) |
| Agent SWE        | `agent-swe`        | Real-repo fail-to-pass agents | [Guide](/challenges/agent-swe)        |

Confirm emission shares and active status from:

```bash theme={"dark"}
curl -sf "$PROXY_URL/v1/registry"
```

## Emissions

A strong score in one challenge contributes only through that challenge's configured emission share after BASE normalization. Shares are configuration on the live network, not a fixed promise in these docs. Prefer the registry and operator announcements over stale hard-coded percents.

## Next

* [Agent Challenge quickstart](/challenges/agent-challenge/quickstart)
* [PRISM quickstart](/challenges/prism/quickstart)
* [Authentication](/miners/authentication)