Repository navigation
Releases
v0.2.0 — M2: fact-finding reports on a live panel
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.
v0.1.0 — on-chain core, measured on devnet
An escrow program can buy arbitration for a locked balance, a staked jury panel decides it behind commit-reveal, and the escrow pulls the verdict and moves the money. No key in the system can bend the outcome.
What is in it
verdict_mesh— protocol config, integrator registry with a validated arbitration policy, juror registry against a staked balance, deterministic panel selection, commit-reveal voting, tally with quorum and a single auto-escalation, stake settlement that slashes a losing vote and silence alike, review fee charged up front and paid to the panel that sat.reference_escrow— milestone escrow that buys arbitration instead of implementing its own, pulls the verdict rather than waiting to be told, and makes the loser pay for the hearing out of a bond both sides put up.authority.rsenumerates the program's instructions and asserts none of them can bend a verdict: FR-014 holds by absence of code, not by policy.- Visual prototype on GitHub Pages. Every number in it is invented.
Measured on devnet, 20 disputes
| Criterion | Budget | Measured |
|---|---|---|
| SC-001 · full cycle, dispute to payout | ≤ 300 s | 218 s |
| SC-002 · total fees per cycle | ≤ $0.10 | $0.017 |
| SC-005 · hearings with no manual step | 0 of 20 | 20 of 20 |
| SC-008 · replayed verdicts rejected | 100% | 6 of 6 |
Fees do not depend on the disputed amount or on the number of milestones, so SC-002 has no way to grow with scale. Rent does.
Programs on devnet
| Program | Address |
|---|---|
verdict_mesh |
8WyWpDD1ZbkTRGG6SRcYyWxApPsHaSgWn2SWJQ8xSgxq |
reference_escrow |
4iYF4WRdtuSmjTXH5fSa2ow5WrdeonEoeoY3epypfTHo |
Not in this release, and worth saying out loud when demoing
No AI fact-finding report: a juror votes on raw signatures, blind. No SDK, no second escrow integration, no appeals, no optimistic track. Jurors are our own keys, so panel independence is arithmetic rather than observed. SC-003, SC-004, SC-007, SC-009 and SC-010 are not measured at this milestone by definition.
Known debt with a price on it: VoteCommit accounts are never closed, which costs a juror about 0.0017 SOL of rent per hearing that nobody returns.
No database migration — packages/db does not exist yet.