Re-verify this verdict

Task sequence-07 · build scripted-naive-frontier-v1 · trial judge-sample-2049

◐ Partial Evidence E4 Reproducible

What was judged

Verdict hash: 0x1981ac8ffae65f48ab77be1ed5c7215785bb3f6f33f4e54bae09b9117ef44c19
Trace hash: 0x2f81355168845a044aecea267d2e9fb46ce81632ee95bf3815c3dc7ff4e7051c
Task spec hash: 0x50fcd9218fabc70feef25291435afc0752dc37de364e3833d604855d6e0ca153
Evaluator: 0x6f1b3cdd7035afc9797e9895db335e1bfb1f3b18b9efffa95eea7532e12adcbe · judge v1.0.0
Release: commit 804cee374f3e · image sha256:3901f8033ecc…8029d5 · allow-listed on Ethereum Sepolia
Hardware: None: this run was not inside a TEE. The proof is reproducibility: anyone can recompute it.

Recompute in your browser

Runs the published evaluator in this browser tab on the stored trace. The bundle is only executed if its SHA-256 equals the evaluator digest.

Recompute on your machine

Node.js 20 or later, no install. The kit checks the bundle digest, runs the judge and compares the hashes:

curl -sO https://karatum.com/verify/kit.mjs
node kit.mjs 'judge-sample-2049:sequence-07:scripted-naive-frontier-v1'

From the source tree: pnpm --filter @karatum/judge build rebuilds the bundle byte-for-byte (same digest), then pnpm verify-verdict 'judge-sample-2049:sequence-07:scripted-naive-frontier-v1' also checks the Sepolia attestations and JudgeVerifier.checkVerdict.

Zero-knowledge proof zk-proven on-chain

A succinct proof (SP1 v6.1.0, groth16) shows that the registered judge program, run on this verdict's trace, outputs exactly this verdict hash. Checking it needs neither Karatum nor TEE hardware: ZkJudgeVerifier.check on Ethereum Sepolia returns level 4 ZK_PROVEN. It proves the judging, not that the evidence in the trace is what happened on the fork.

Batch: judge-sample-2049:all:134 · 134 verdicts · leaf #128
Batch root: 0xe34d4ed032465fe51904e577ad97f763669b50486b99ed3f38d24aad4f622983
Program vkey: 0x002d2d2187a66f42137573dd444681fbcfd7b07e9534a1ace7f6ed70ef922ecd · allow-listed in EvaluatorRegistry
Proof: 0x4388a21c00000000…48c73e (356 bytes) · 91,824,236 RISC-V cycles · proved in 54.4 min on CPU
Inclusion: leaf 0xc61cf5240f8f…f2c7f0 · 4 sibling hashes
On-chain: submitBatch 0x32afdb4320…a4fab7 · block 11933344 · 812,975 gas · ZkJudgeVerifier

cast call 0xab179e5a8BA1b5B4a361665d15a9cBFE7402735c \
  "check(bytes32,bytes32,bytes32,bytes32[])(uint8,bytes32)" \
  0xe34d4ed032465fe51904e577ad97f763669b50486b99ed3f38d24aad4f622983 \
  0x2f81355168845a044aecea267d2e9fb46ce81632ee95bf3815c3dc7ff4e7051c \
  0x1981ac8ffae65f48ab77be1ed5c7215785bb3f6f33f4e54bae09b9117ef44c19 \
  "[0x32d48fb32b1cf8663f4ebb96405101a2cb145c5814d380ded49013e82fb0bebd,0xf955cf06bff4ac66e9196ddf8c5789fcd0f093bda680b502830239e965f6f808,0x5fd55df80e78e94b16c008bafbdf4dd86c1226903e85283a8c660a4bef72f623,0x49e6daa7361fddb5eafabc4dd94fed732c4049a5edaefe074a72aa065326fb16]" --rpc-url https://ethereum-sepolia-rpc.publicnode.com

How the zk-proven judge works, costs and all batches · inclusion proof as JSON: /v1/zkjudge/verdicts/…

On-chain

Verdict attestation: 0x3274e6d0f4fe…00596d
Judge provenance: 0x951c8612b059…263229
Verifier: JudgeVerifier (checkVerdict(verdictUid, provenanceUid)) and EvaluatorRegistry

How the verifiable judge works · Verdict details