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

# Bounty Challenge

> Miner-facing guide for Bounty Challenge: owner-set project briefs, GitHub submissions, human review, emissions.

Bounty Challenge is a secondary challenge on BASE for open-ended project work that needs **human judgment**. An owner publishes a brief, miners submit finished work (typically as GitHub links), and the owner reviews and assigns emissions to hotkeys that produced the best results. The subnet then normalizes those challenge outputs into netuid 100 weights.

**Status:** Secondary / experimental relative to Agent Challenge and PRISM. Confirm the live slug and emission share via the registry before registering spend.

## What it is

| Item           | Detail                                                                             |
| -------------- | ---------------------------------------------------------------------------------- |
| Slug (typical) | `bounty-challenge`                                                                 |
| Artifact       | Finished project work, usually linked from a submission record (challenge-defined) |
| Scoring        | Owner review assigns emissions; not a single automatic unit test score             |
| Good for       | Product flows, UX work, open-ended builds where auto-graders are insufficient      |

## Miner path

<Steps>
  <Step title="Register on BASE">
    Hotkey on netuid 100. See [Wallet and registration](/miners/wallet-registration).
  </Step>

  <Step title="Discover open bounties">
    Use the challenge public routes under `/challenges/bounty-challenge/...` (exact paths in the challenge repository). List live challenges:

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

  <Step title="Build the deliverable">
    Implement the owner brief in a repository the challenge accepts (commonly a public GitHub URL plus metadata).
  </Step>

  <Step title="Submit and monitor">
    Follow the challenge signing and submit contract. Identity and subnet proxy signing patterns: [Authentication](/miners/authentication). Track owner review status on challenge endpoints, not only the subnet layer.
  </Step>
</Steps>

There is no Base-global "run miner" binary for bounties. Submission format and review UX are **challenge-owned**.

## Costs and expectations

* Chain registration and wallet security are miner-side
* Compute spends (if any) depend on the bounty, not a subnet TEE mandate
* Owner discretion means timelines and feedback differ from automatic challenges

## Repository

[`BaseIntelligence/bounty-challenge`](https://github.com/BaseIntelligence/bounty-challenge)

## Related

* [All challenges](/challenges/overview)
* [Data Fabrication](/challenges/data-fabrication)
* [Miner hub](/miners/overview)