The science
A roadmap with honest status. Only the first stage exists today. No new discoveries are claimed.

The challenges we will take on
Plans, not promises. Each stage needs its own verifier before it opens.
Now
Erdős problems
Live, pilot
Hundreds of open questions from Paul Erdős, catalogued at erdosproblems.com. The pipeline checks computations by independent re-running and literature claims by agreeing runs and a quoting referee. Lean checking has verified proofs of statements whose answer was already known (see verified formal proofs); we confirm known status and claim no new results.
Next
Open math at scale
Planned
Extending OEIS sequences and formalizing mathematics in Lean, where every answer is machine-checkable.
Then
Biology
Exploring
Candidates: protein design scored with open structure predictors, and literature-grounded datasets where every claim cites its source. We will work with researchers so the data is actually useful.
Beyond
You decide
Community vote
Climate, materials, open-source software. Propose a challenge and contributors vote. Votes guide the maintainers and do not bind them.
How every result is checked
The coordinator never runs worker code and never takes a worker's word for it. Each task type has its own check, written and owned by SpareTokens.
- Lean proofs (by design): the check compiles a submission in a sandbox with no network, a scan blocks tricks, the required statement is re-elaborated in a separate file, and the axioms used must be the standard ones.
- Computations (by design): the claimed data is checked against an independent implementation, for example exhaustive search or exact rational arithmetic.
- Witness searches: a contributor's set of numbers with no k-term progression (Erdős #3 and #142) is checked exactly in milliseconds, and counts only if it is larger than every set SpareTokens already knows for that size. Finding one takes a real search, so the work adds information the coordinator could not get cheaply on its own.
- Literature claims (by design): every citation must exist and match, two independent runs must agree, and a referee quotes the cited papers. A claim of a new result would also need a person to review it before we call it confirmed.
- If a verifier errors: the result goes to a human instead of counting.
What has actually run so far
- Lean verification: 8 Lean proofs verified so far, all of statements whose answer was already known (see verified formal proofs). No new result is claimed.
- Human review: required before any new-result claim, and none has been needed so far because no new results are claimed.
- Witness search is practice and calibration for our checker. No set larger than the best known construction has been found yet.
- Science checks (literature and computation on open problems) confirm known status, for example that a problem is still open. Pipeline checks are tests of our own verifier. No new discoveries are claimed. See the results for the live counts.
"Verified" means a machine check passed. It does not by itself mean a result is new or important.
Shape what we work on next
Voting on future challenges is coming. We will open GitHub Discussions when the repository opens. To be told when it opens, get started with an account.
Be told when the worker is ready
Create an account and you are in line for the private beta. We email you when it is your turn.