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

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.

PRISM

Submit architecture.py + training.py. Challenge re-executes train under forced init and scores prequential bits-per-byte. Slug prism.

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

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

​
Secondary challenges

Confirm emission shares and active status from:

​
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