Source-Grounded Content Claim Verifier

A GenLayer Intelligent Contract for verifying claims against governed web sources, producing reusable verification receipts, and allowing other parties to rely on or challenge those receipts.

Overview

The contract is designed for workflows where a claim should not be accepted solely from model memory.

Instead, the contract:

1. Governs which web source can become authoritative.
2. Requires independent attestations before a source becomes authoritative.
3. Fetches the authoritative source during verification.
4. Hashes the retrieved source content.
5. Uses a non-deterministic evaluation to classify the claim.
6. Validates the result independently.
7. Creates a reusable receipt containing the verification evidence.
8. Allows another party to rely on the receipt.
9. Allows another party to challenge the receipt.
10. Blocks downstream reliance when a receipt is challenged.
11. Allows the source itself to be disputed and placed into review.

Why Source Governance Matters

A developer-selected URL should not automatically be treated as authoritative.

The contract therefore starts a configured source in:

proposed

A source becomes:

authoritative

only after two distinct addresses attest to that source.

Duplicate attestations from the same address do not increase the attestation count.

A source can also be disputed. A dispute changes its status to:

review_required

Verification is blocked unless the active source is currently authoritative.

Verification Flow

Proposed Source
      |
      v
Independent Attestation #1
      |
      v
Independent Attestation #2
      |
      v
Authoritative Source
      |
      v
Activate Source
      |
      v
Verify Claim
      |
      +--> Fetch Source
      |
      +--> Hash Source Content
      |
      +--> Evaluate Claim
      |
      +--> Independent Validation
      |
      v
Verification Receipt
      |
      +----------------------+
      |                      |
      v                      v
Another Party          Another Party
Relies On Receipt      Challenges Receipt
      |                      |
      v                      v
Workflow Reliance      review_required
                             |
                             v
                       Further reliance blocked