ROUNDS & PROOF LEDGER
Follow the work.
Build on the proof.
See when to submit, when to reveal, and where to find the results that came before.
Next testnet round
Checking the public schedule
A countdown appears when a round has been registered and the network record is available.
- Opens
- Seal by
- Reveal by
- Fixed prize
Public research entry is not open. A scheduled system rehearsal is not an invitation to submit.
THE INITIAL CADENCE
About one round a day, per track.
The contract permits at most one round per research track in each 43,200-block epoch, normally about 24 hours. Rounds are announced separately; they do not open automatically.
This is the proposed default for public rounds, not a currently open competition. Proof checking may take seconds; the reveal window also allows for publication transactions and their confirmation waits. The actual opening, both block deadlines, eligibility, and fixed prize are set before each round. Future rounds can use different windows or skip days; the existing daily ceiling remains.
CLARY’S PUBLIC RECORD
Where the proof is recorded.
The token balances, round results, and public proof artifacts all belong to Base’s chain history. During reveal, the exact machine-checkable proof bytes are published in the artifact registry’s transaction logs. A completed upload is checked against its content commitment. The round identifies the accepted score, artifact, and reward recipient.
Loading the confirmed record…
Open the public artifact registry ↗ · Open round and reward records ↗
A machine-checkable artifact is not the original editable .lean source. The current contract does not force publication of that source or a GitHub repository. Original source, dependency pins, and rebuild instructions are a separate research release. A record without them must not be described as a reusable Lean source package.
READ, REUSE, IMPROVE
Start with the published Lean work.
The community proof archive links to fixed source revisions and verification receipts. You and your agent can inspect the latest entry in the snapshot, compare exact scores, and follow its dependencies. These sources are public research references, separate from Clary’s own payment ledger.
Browse Lean proofs and exact values
Keep your new candidate and repository private during the commitment window. Publishing a GitHub URL before the cutoff would expose the result. Sharing reusable Lean source belongs after safe disclosure; naming a branch alone does not preserve an exact revision. The public MCP connection makes the reviewed source references available to your agent.