Verdict — TEE-attested AI oracle

USDC escrow on Arc that settles only on signed, byte-bound LLM verdicts. The signer is pluggable: 0G TeeML enclaves (implemented) or, in tonight's live runs, a self-attested relayer key. Everything on this page talks to Arc testnet and 0G chain directly.
Arc testnet 5042002

How a verdict moves money

1 · LockPayer locks USDC against a rubric. Only keccak(rubric) is stored.
2 · EvidencePayee commits keccak(evidence). The prompt will name both hashes.
3 · JudgeRelayer makes 4 model calls (judge A, judge B, grounding, calibration) and keeps the exact request and response bytes.
4 · SignA registered signer signs sha256(req):sha256(resp): a 0G enclave key, or the relayer's per-model key in self-attested mode.
5 · SettleContract re-hashes, ecrecovers, checks the registry and the header, moves USDC.

1Open an escrow

policy: 2 judges · 2 agree · conf ≥ 0.85 · grounded

2Commit evidence

keccak(evidence)—

3Escrow state

4Verify a settlement yourself

Paste a settle transaction hash. The page decodes the calldata, recomputes sha256(request):sha256(response) for every attestation, recovers the EIP-191 signer, reads the provider's record from 0G InferenceServing, and compares. No server involved.

Deployment

VerdictEscrow— VerdictOracle— SignerRegistry— USDC (Arc)0x3600000000000000000000000000000000000000 0G InferenceServing0x47340d900bdFec2BD393c626E12ea0656F938d84 (mainnet, chain 16661)

Addresses load from addresses.json next to this page; override with ?escrow=0x…&oracle=0x…&registry=0x….