Repository navigation
What's new
Fact-finding reports for jurors, on a live panel — when a dispute opens, jurors get a structured report built from the escrow's on-chain history instead of raw transactions, and anyone can open the panel on devnet without a wallet.
Details
- Disputes are mirrored from devnet into Postgres, including those opened through CPI; evidence is collected by
escrow_ref. - The reporter (
claude-opus-5) separates on-chain facts, party claims and contradictions; every fact links to the transaction or account that supports it, and a fact whose source is not in the evidence is shown as unconfirmed. - The report's SHA-256 fingerprint is attested on chain by a reporter-only instruction, once per dispute; the API serves a report only together with that on-chain check (
FR-017b). - If the model is down, disputes still go to a vote and the panel says why there is no report (
FR-018). - The panel reads the live API: hearing list, report, evidence, settlement; jurors seal and reveal votes from their own wallet (Phantom, Solflare, Backpack via Wallet Standard).
- The project page now sits at the Pages root and the panel at
/app/. - Measured: report available in p95 24.9 s (SC-003); 0 of 111 confirmed facts contradicted by the chain on 20 disputes with a known answer (SC-007,
fixtures/disputes/); first panel screen in 0.55–1.13 s (SC-010).
Files changed
programs/verdict-mesh/—attest_reportapps/api/src/— watcher, evidence, reporter, settlement,/disputesand/disputes/:pda/reportroutes,sc007/packages/db/— Postgres schema with RLS, migrations0000and0001apps/web/src/— panel on the API, wallet voting, landing pagerender.yaml,.github/workflows/pages.yml— API on Render, Pages pointed at itfixtures/disputes/— the SC-007 set and its measured reports
Migration
✅ No migration needed — 0000 and 0001 are already applied to the hosted database.