Verify a round
Recompute the digest, compare it with the ledger, and check a receipt against the enclave.
Run the same four checks here.
No install, no accountThese are the checks `npm run judge` runs, and this page runs the same ruleset file the command line does — not a port of it. Three of the four need no network at all: the bands are recomputed from the raw submissions in your browser, the digest is rehashed from the published bytes, and two deliberately tampered inputs are put through to confirm this can say no. The third reads the digest back off Solana devnet through a public endpoint we do not run.
01
Recompute the digest
SHA-256 over the exact bytes of the published round, computed locally with the Web Crypto API.
anchored on solana
e4f528ad321626b2daf9b667188937609cd160a21a739d542eabd44a2f40beef
02
Read the anchor
The same digest, written to Solana devnet as a memo at the slot shown. Public, timestamped, and not ours to edit.
slot
492821211
block time
2026-09-04 03:20:46 UTC
signature
5uczxVJUm4zjwDms6R5eDC9H1G3gypRUuDA1p2B1x14bXP8QCezrFxZLgfRzfGCJLG3HDJ7ubfsWpiZBG4AJE3Hf
03
Prove a receipt belongs
Each accepted row returns a commitment. Ask whether that commitment is in the round, and whether its cell reached a published band.
64 hexadecimal characters, as returned when the row was accepted.
The receipt lookup on this page answers from the sample set shipped with the site, so it works offline and spends nobody's credits. The authoritative answer comes from the enclave: npm run verify in the repository asks the contract directly, and includes a deliberately forged commitment as a control.