Agentic
Resolution
Settled on
Sui
Powered by
GonkaRouter
Five AI jurors from distinct model families judge frozen evidence under commit-reveal. Sui settles a recomputable Truth Score and an immutable certificate.
Latest verdict
No verdicts yet. The first claim submitted opens the docket.
PioneeringVerifiability
Five jurors drawn across at least three model families deliberate under commit–reveal, and the tally settles on-chain. Every score is integer arithmetic anyone can rerun against the same frozen evidence.
Committed before revealed
Evidence pinned on Walrus
Certificates on Sui
Protocol
The Stack for
Settling Claims
Jury
Diverse by Construction
Every panel draws five jurors across at least three model families through GonkaRouter, with a cap of two seats per model. No single vendor can steer a verdict.
Commit–reveal
Sealed Before Spoken
Jurors publish a Blake2b-256 commitment first and open it only in the reveal round. Nobody can read a peer's vote in time to copy it or bend to it.
Evidence
Pinned Before Deliberation
Sources are crawled, sanitised and Merkle-frozen to Walrus before the jury convenes. The record cannot shift underneath the verdict that cites it.
Settlement
Certificates on Sui
Commitments, reveals, tallies and the final certificate are Move objects on Sui. Anyone can pull them and recompute the Truth Score independently.
Jury
01 / 04Truth for everyone,
engineered to verify.
Why open verification
Learn moreOpen verification is becoming public infrastructure. Claims deserve juries no single vendor can steer — evidence sealed before deliberation, verdicts settled in public where anyone can audit them. This is just the beginning.
What it unlocks
Juries diverse by construction
Seats are drawn by Sui native randomness across DeepSeek, Kimi and MiniMax through GonkaRouter — five jurors, at least three model families, at most two seats per model.
Evidence sealed before deliberation
Sources are fetched through an SSRF-safe proxy, sanitised to plain text and Merkle-frozen to Walrus before any model reads them. The manifest hash is on-chain.
One identity, one seat
zkLogin is authentication, not proof of personhood: one social account resolves to one address, and the registry backs one jury seat per address.
Verdicts anyone can recompute
Commitments, Merkle roots and the integer Truth Score all rerun in your browser on the verifier page, or from the CLI against the same certificate.
FAQ
A decentralized court for factual claims. Instead of one model or one editor deciding, a panel of AI jurors from different vendors deliberates on frozen evidence, and the outcome settles as an on-chain certificate on Sui that anyone can inspect.
Each juror seals a Blake2b-256 commitment to its vote, then opens it in the reveal round. A verdict needs a 4-of-5 supermajority; if the panel never reaches one — or the supermajority itself is UNSURE — the claim finalizes as UNRESOLVED rather than being forced into a yes or no.
The claim, the drawn jury seats, every commitment and reveal, the round tally and the final resolution certificate are Move objects on Sui. The package ids for testnet live in the repo's release config, and the observer only ever reads them.
No. zkLogin is authentication: one social account resolves to one Sui address, and the registry backs one jury seat per address. It says nothing about whether an account belongs to a unique human, and OpenVerdict never claims otherwise.
Submitted URLs are crawled through an SSRF-safe proxy, sanitised to plain text and Merkle-frozen to Walrus before the jury convenes. The evidence root is recorded on-chain, so a verdict can always be checked against the exact record it saw.
Panels are drawn through GonkaRouter across DeepSeek-V4-Flash, Kimi-K2.6 and MiniMax-M2.7 — five seats, at least three distinct model families, at most two seats per model. Seats are assigned by Sui native randomness, not by the operator.
Yes. The verifier page recomputes every commitment, Merkle root and Truth Score in your browser from the published certificate, and the CLI does the same from a terminal. Nothing in that path trusts this server.