ProofCourt

Evidence. Consensus.
Verdict.

AI-powered insurance adjudication built on GenLayer.

Submit evidence. Let GenLayer validators review. Receive a transparent verdict.

ILLUSTRATIVE ADJUDICATION VISUAL
  1. 01Claim
  2. 02Evidence
  3. 03Verification
  4. 04Consensus
  5. 05Verdict
  6. 06Finality
SCROLL-DRIVEN PRODUCT EXPLAINERClaim

The problem

When Digital Claims Become Disputed

Digital disputes are difficult to resolve because evidence exists, but trust does not. Traditional systems struggle when real-world evidence requires reasoning and judgment.

ProofCourt helps resolve agent, wallet, and continuity disputes through evidence, defined policy rules, and GenLayer consensus.

Claim categories

Three kinds of digital responsibility.

01

Agent Failure

AI agents can act autonomously. When they fail, ProofCourt helps evaluate what happened through evidence and consensus.

  • AI Trading Agent Loss
  • Autonomous Execution Error
  • Agent Misconduct
  • Unauthorized Transaction
  • AI Strategy Failure
  • Data Leak Incident
02

Wallet Recovery

Lost devices, failed backups, and disputed recovery can leave digital assets inaccessible. ProofCourt replaces guesswork with an evidence-led process.

  • Lost Device
  • Hardware Wallet Failure
  • Recovery Phrase Problem
  • Backup Failure
  • Multi-Sig Access Failure
  • Wallet Corruption
03

Digital Continuity

Inheritance, beneficiary access, and long-term asset continuity create disputes conventional smart contracts cannot easily resolve.

  • Beneficiary Access Request
  • Inheritance Claim
  • Account Continuity Request
  • Emergency Recovery Request
  • Family Verification
  • Estate Settlement

The solution

ProofCourt Solves All Three

ProofCourt combines evidence integrity, independent verification where possible, and GenLayer consensus to evaluate agent liability, wallet recovery, and digital continuity claims.

01

Submit Claim

Describe the dispute and its claimed loss.

02

Upload Evidence

Private files remain off-chain.

03

Evidence Integrity

SHA-256 fingerprints the submitted bytes.

04

Evidence Verification

Objective references are checked where supported.

05

GenLayer Consensus

Validators evaluate the canonical claim.

06

Verdict

APPROVED, DENIED, or ESCALATED after finality.

Integrity is not authenticity. A SHA-256 hash confirms the submitted file's bytes have not changed; it does not by itself prove the source, authenticity, or truth of the content.

The adjudication path

From a claim to authoritative finality.

A visual explanation of ProofCourt’s process. It is not a live claim status.

SYSTEM EXPLAINER
  1. 01ClaimCurrent chapter
  2. 02EvidenceNext
  3. 03VerificationNext
  4. 04ConsensusNext
  5. 05VerdictNext
  6. 06FinalityNext
Independent validator review

ProofCourt renders authoritative outcomes only when they are returned by the existing claim workflow.

Evidence verification

Who verifies the evidence?

The decision starts with what can be proven. Anyone can upload a file; that does not make it true.

  1. 01 Hash
    Exact submitted bytes
  2. 02 Content verification
    Supported public immutable evidence
  3. 03 Blockchain verification
    Objective on-chain facts
  4. 04 Consensus
    Independent validator decision
  5. 05 Finality
    Authoritative lifecycle result
SHA-256

Evidence Integrity

Confirms the exact evidence submitted and detects later modification. It does not prove a file is truthful.

GenLayer Validators

Independent Review

Validators independently evaluate the canonical claim under the contract’s defined rules.

Blockchain / Trusted Sources

Independent Sources

When a supported reference is supplied, ProofCourt can check objective on-chain transaction metadata. Broader sources are future work.

Phase 2 boundary: ProofCourt can verify evidence integrity with SHA-256, perform GenLayer validator-backed content assessment for supported immutable public TXT evidence, and perform objective on-chain transaction verification when a valid transaction reference is supplied. These checks do not by themselves prove that arbitrary uploaded documents, images, receipts, or logs are truthful or authentic, or that they are related to a transaction.

Why GenLayer

Evidence needs decentralized reasoning.

Traditional smart contracts execute deterministic rules. ProofCourt needs to evaluate evidence and judgment, while keeping final authority decentralized.

GenLayer Intelligent Contracts can use web data, LLM reasoning, image processing, and blockchain information where an implementation deliberately supplies and validates them. Validators independently evaluate the proposed result through GenLayer’s consensus and equivalence model; ProofCourt never treats one centralized AI response as the verdict.

ProofCourt at a glance

Insurance adjudication powered by evidence and GenLayer consensus.

01

What is ProofCourt?

Insurance adjudication powered by evidence and GenLayer consensus.

02

Who is it for?

Agent operators, wallet owners, beneficiaries, and digital asset holders.

03

How does it work?

Evidence is submitted, verified where possible, and evaluated through validator consensus.

04

What is the outcome?

APPROVED, DENIED, or ESCALATED—only after an authoritative finalized result.

Roadmap

Building the future of decentralized insurance adjudication.

PHASE 01
COMPLETED

Evidence → Consensus → Verdict

The working MVP: private evidence, canonical claims, GenLayer consensus, and an authoritative verdict.

PHASE 02
COMPLETED

Evidence Verification Layer

Read-only objective GenLayer transaction metadata checks add a bounded verification layer.

PHASE 03
FUTURE

Multi-Source Evidence Intelligence

External sources, agent logs, additional model providers, and attestations.

PHASE 04
FUTURE

Insurance Pool & Payouts

Policies, premiums, coverage limits, claim eligibility, and payouts.

PHASE 05
FUTURE

Decentralized Insurance Marketplace

Liquidity providers, risk pools, coverage markets, and decentralized capital allocation.

A court for disputed digital claims

Make your case.

Start with a safe simulation, or submit a claim to the configured live GenLayer workflow.