Who checks the checker?

Every new Karatum verdict is a pure function of its trace: the task spec and the chain or code evidence the runner collected. The function is a single published JavaScript file, the evaluator bundle. Its SHA-256 is the evaluator digest. It builds byte-for-byte from the source commit, and the owner allow-lists it in an on-chain registry on Ethereum Sepolia. Anyone can download a verdict's trace, run the same bytes and get the same verdict hash that was attested.

What this proves: given the trace, the verdict follows from the published code. What it does not prove by itself: that the trace's evidence was collected honestly from the Mirror fork. That needs a hardware TEE quote over the run (methodology: docs/methodology/verifiable-judge.md in the Karatum repository). Verdicts decided before October 2026 have no trace.

Evaluator releases

Digest (sha256 of the bundle)VersionCommitOn-chain
0x6f1b3cdd7035afc9…1.0.0804cee374f3eallow-listed

Latest re-verification run

reverify-2026-10-16

  • No trace (older verdicts): stored fields re-hashed and compared with the Sepolia attestation: 100/100 match
  • Recomputed from trace with the published bundle: 100/100 match

Recent verdicts with a trace

Contracts (Ethereum Sepolia)