Skip to main content
A 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:
get_weights is how BASE reads raw hotkey weights. It is token-authenticated and not exposed on the public proxy.

​
Primary challenges

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 →

​
Additional challenges

Owner-reviewed project bounties that need human judgment. Guide →
Dataset-generation harnesses for agentic coding conversations. Guide →
Real repositories as fail-to-pass agent benchmarks. Guide →

​
How a challenge plugs in

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

Challenges tab

Full catalog and miner packs.

How the subnet works

End-to-end flow.