Skip to main content
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

​
Miner path

1

Register on BASE

Hotkey on netuid 100. See Wallet and registration.
2

Discover open bounties

Use the challenge public routes under /challenges/bounty-challenge/... (exact paths in the challenge repository). List live challenges:
3

Build the deliverable

Implement the owner brief in a repository the challenge accepts (commonly a public GitHub URL plus metadata).
4

Submit and monitor

Follow the challenge signing and submit contract. Identity and subnet proxy signing patterns: Authentication. Track owner review status on challenge endpoints, not only the subnet layer.
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