Overview
SourceJury stores a claim, source references, authenticated evidence commitments, source assessments, a verdict, rationale, revision, and challenge state. Reading the court does not require a wallet.
The interface uses finalized contract state for durable results. It does not synthesize a replacement verdict when RPC data is unavailable.
Evidence policies
DIRECT_SOURCE_V1
A primary source is evaluated directly. The result can support, contradict, or fail to provide enough relevant evidence.
CORROBORATED_V1
Primary and corroborating evidence are evaluated together. The UI requires a corroborating URL when this policy is selected. Distinct hosts provide source diversity only; they do not prove independent ownership, editorial independence, or factual provenance.
Authenticated evidence commitments
Every bounded evidence body used for adjudication is preserved as an immutable snapshot and committed with SHA-256 over the exact UTF-8 rendered text. Case state records the snapshot ID, digest, and content length.
The case page reads the stored snapshot, asks the contract to verify it, and independently recomputes both the content digest and snapshot ID in the browser. Evidence above the supported 8,000-character decision bound is never silently truncated; it fails closed as CONTENT_TOO_LARGE.
Verdicts
- SUPPORTED — evidence supports the claim.
- CONTRADICTED — relevant evidence opposes the claim.
- INSUFFICIENT — evidence is unavailable, irrelevant, conflicting, oversized, or otherwise inadequate for a directional verdict.
Challenge lifecycle
A challenge references a case, challenger, counter-evidence URL, and explanatory note. It is evaluated against the authenticated original evidence snapshots rather than substituting a later webpage version.
The contract separately rechecks the live original URLs and records whether each is unchanged, modified, unavailable, or too large. A modified live page never replaces the evidence originally adjudicated.
This is a bounded counter-evidence downgrade mechanism, not complete case reconsideration. One challenge may downgrade a directional verdict to INSUFFICIENT, but cannot directly reverse SUPPORTED into CONTRADICTED or vice versa.
Wallet and network
SourceJury discovers installed EIP-6963 wallets and falls back to an injected EIP-1193 provider. The wallet can add or switch to Studio Devnet before a write.
A write performs a fresh method-specific fee estimate, asks the wallet to sign, then waits for finalization before refreshing durable state.
Public contract methods
get_protocol_infoViewProtocol metadata and supported policies.
get_case_countViewNumber of persisted cases.
get_challenge_countViewNumber of persisted challenges.
get_case(id)ViewComplete case state and verdict history.
get_challenge(id)ViewComplete challenge state and outcome.
get_evidence_snapshot(id)ViewExact bounded evidence content and SHA-256 commitment used for adjudication.
verify_evidence_snapshot(id)ViewContract-side verification of snapshot integrity.
create_case(...)WritePersist a claim and evidence references.
evaluate_case(id)WriteEvaluate a case through consensus.
open_challenge(...)WriteAttach bounded counter-evidence to authenticated original evidence.
resolve_challenge(id)WriteResolve counter-evidence through consensus.
Certified backend binding
- Contract
- 0x6Dbe8007192EF981a61fFf540d873F03cD8E3BaE
- Contract SHA-256
- b70415770e5d4a9c1cd5371f1e400c3ae073dd5ac3c8f07b0de236ee5f9c3241
- Backend checkpoint
- f6a2b86513e41de0f705c0c0bae527daa843eb7f
- Progress 6 certification
- 74d0f8c8ffc7718d894516bc98ec9d2fbe833e9a21681f2f6bb08caf731d343d