Topics · Domain workflow
Forensics teams hash the candidate media, verify the receipt offline, and read Sigil state — determining whether the asset matches the signed path after leaving the original surface.
Concrete scenario
A newsroom receives a viral video clip. The uploader claims it shows an event timestamped yesterday. Editors have only the MP4 forwarded through messaging apps — EXIF is gone, thumbnails were re-encoded, compression artifacts abound, and the origin account is anonymous.
Problem
Media spreads faster than metadata. Re-uploads, crops, screen shots, and CDN transforms strip context; reviewers still need to know whether visible pixels match a signed version independent of the original hosting app.
Mechanism
Receipts bind content fingerprints, transformation trails, and public claims at capture or publish time. C2PA-compatible bridge artifacts can compose in ext_* commitments while ZK-SNAP remains the portable verification kernel for machine actions around the asset.
Verifiable outcome
Scope boundary
Provenance receipts prove signed capture and publish facts — not semantic truth of depicted events, deepfake detection alone, or editorial judgment about newsworthiness.