PLAIN-LANGUAGE GUIDE
From question to final ruling
Follow one page at a time. Every screen explains when a wallet is required and when an action becomes final.
File the proposal
Choose a unique ID, question, allowed answers, two HTTPS sources, and a challenge period.
Request assessment
Validators retrieve both records, verify a bounded ruling, and store source-linked digests.
Challenge if needed
Before the deadline, anyone may add conflicting evidence from a different hostname.
Finalize the record
After the protected window—or after a challenge—finalization stores the canonical outcome.
Verify publicly
Inspect the final answer, findings, sources, and content digests without a wallet.
SAFETY CHECKLIST
What the contract enforces
- Case IDs are normalized and duplicates are rejected.
- Original evidence must come from two different HTTPS hostnames.
- Validators independently refetch evidence and verify leader-proposed fields.
- Every assessed record keeps a SHA-256 digest bound to source order.
- A challenge requires a third hostname and must arrive before the deadline.
- Eligible finalization is permissionless so a missing filer cannot stall a case.