Jury
Resolution

An adversarial AI jury protocol for factual disputes, not an agent swarm. Instead of one model or one editor deciding, a committee of five juror seats drawn on-chain from three model families researches the claim independently (every search and page open is executed by the engine and recorded), seals a secret ballot under commit-reveal, cross-examines a deadlock over the frozen evidence, and the outcome settles as a resolution certificate on Sui that anyone can recompute.

Each juror seals a Blake2b-256 commitment to its vote, then opens it in the reveal round, so no juror can anchor on or herd around another's reasoning before sealing its own stance. A verdict needs a 4-of-5 quorum; a split round goes to a bounded cross-examination (three exchanges at most, citing only the frozen record) and a second sealed ballot; if the quorum is still missing, or the quorum 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.

Staking opens a juror seat and costs real money: the staker posts at least 0.1 SUI as that seat's bond, receives the seat's jury rewards, and keeps the bond locked while the seat is active. Unstaking deactivates the seat and returns the bond 24 hours later; slashing the bond for proven protocol violations is specified, not yet enforced on chain. Any account can stake, on as many seats as it likes: a browser wallet, an operator key, or a Google sign-in through zkLogin, and OpenVerdict sponsors the gas. The draw caps diversity instead: at most two seats per model family and one per operational signing key, with no cap per staker. zkLogin is authentication only, there so people without a wallet can stake too.

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. Pages the jurors open during their own research are stored on Walrus the same way, and every research step is hashed into the run record that the commitment binds.

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.

Today, the OpenVerdict engine executes every juror run itself, and all AI reasoning goes through GonkaRouter only: the adapter refuses any other inference host in code, and a juror that cannot reach Gonka fails closed instead of falling back. Jurors are standardized seats, not user-owned bots: prompts and tool policies are hashed into on-chain manifests, so nobody, including the operator, can steer a seat without breaking hashes anyone can recheck. Trust here comes from verifiability rather than decentralized execution; an attested executor (Sui Nautilus) is the disclosed roadmap step.

Requesters fund a claim's budgets in SUI when it is created; the public demo form is a team-subsidized tier of the same flow. At settlement the committee budget splits across the seats that validly revealed, as one-time payout tickets: commit late, fail the schema or refuse to reveal, and that seat earns nothing. A seat's tickets go to whoever staked on it, so opening a seat with 0.1 SUI is how anyone earns from jury work. Pooling several stakers behind one seat with pro-rata payouts is documented direction rather than shipped code, and majority-only winner pay is rejected by design, so juries are never paid for herding.

No vote is ever invented for it. Since round two at the table, a verification is all or nothing: a juror error at a binding step voids the whole attempt, the failure and the seat's research trail stay public, and the engine relaunches a fresh attempt once all three model families and web search answer a health probe, up to three attempts. Nothing partial is ever finalized.

Yes. The verifier page recomputes every commitment, Merkle root, run hash and Truth Score in your browser from the published record (15 checks per juror run), can resend a juror's exact recorded conversation to the same model, and can open a sealed juror bundle through Seal once its reveal deadline has passed. The CLI does the same from a terminal. Nothing in that path trusts this server.