CAPTURE PROOF
zkShot capture
Session-boundBeacon-anchored earliest timeSelf-asserted locationCamera not attested
Capture details⌄
Capture time
Wed, 12 Aug 2026 00:03:59 GMT (claimed by device)
Received by server
Wed, 12 Aug 2026 00:04:16 GMT
Time anchor
proven no earlier than Wed, 12 Aug 2026 00:03:30 GMT — drand round 6368733 (unpredictable beacon bound into the proof)
Location
40.75232, -74.00840 ±18m map (claimed by device, radius bound into the proof)
SHA-256
17ac1b2a2c6182b8d850ffe09ee9ff23f5209af8c1bb1be1c973c3f7e94e230c
Poseidon commitment
16830329867029812764106307752529449576986508744892269249916921559549712119743

zkVerify verification

ANCHORED ON BASE ✓
⏳Re-hashing image in your browser…
  1. ✓
    Queued
  2. ✓
    Valid
  3. ✓
    Submitted
  4. ✓
    IncludedInBlock
  5. ✓
    Finalized
  6. ✓
    Aggregated
  7. ✓
    Anchored on Base
zkVerify transaction

0x79f954463f7f2605334ae5bb43af2b20556a9ea51ef3de65dd5299a848b8b3e7

What this proof shows — and what it doesn't

A zero-knowledge proof, verified on the zkVerify network, shows that someone holding a one-time session secret bound this exact image (by its SHA-256 hash), the capture timestamp, the location (if shared), and an unpredictable public beacon (if reachable) together at proving time inside the zkShot capture flow. The beacon, when present, proves the commitment could not have been formed before the time shown in the Time anchor row. If the image integrity check above passes, the image displayed here is byte-identical to the one committed in that proof.

It does not cryptographically prove the photo came from a physical camera sensor, nor that the timestamp or location are accurate — browsers cannot access hardware attestation, and both values are asserted by the capturing device. It also says nothing about what was in front of the camera: photographing a printed picture, another screen, or any staged scene produces an equally valid capture proof of a fake image. Treat it as evidence of an unbroken chain from the zkShot capture session, not as forensic proof of origin or authenticity.

Verification happens at source: this page checks the originally stored bytes. Copies of the photo shared on social platforms are recompressed in transit and cannot be re-verified byte-for-byte — the proof travels with this link, not with the image. For independent verification without trusting this site, download the verification bundle below.

⬇ Download verification bundle (image + proof + keys — verifiable offline)