CAPTURE PROOF
zkShot capture
Session-boundBeacon-anchored earliest timeSelf-asserted locationCamera not attested
Capture details⌄
Capture time
Tue, 11 Aug 2026 14:50:01 GMT (claimed by device)
Received by server
Tue, 11 Aug 2026 14:50:01 GMT
Time anchor
proven no earlier than Tue, 11 Aug 2026 14:49:30 GMT — drand round 6367625 (unpredictable beacon bound into the proof)
Location
40.73874, -74.00366 map (claimed by device)
SHA-256
052270c3dd0fc56d52eaf75ad4f3a56d1b3df3af607e402d1bfc64c0b6abf359
Poseidon commitment
4663871495944848740347417506536326108818442088491077741903822099780949426198

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

0xee7fd451a01fa1b0cb42ec687e51d6b3cad1d01348269f1c2d1758e2e523ed50

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)
zkShot — photo with a zero-knowledge capture proof