CAPTURE PROOF
zkShot capture
Session-boundBeacon-anchored earliest timeSelf-asserted locationCamera not attested
Capture details⌄
Capture time
Wed, 12 Aug 2026 04:52:42 GMT (claimed by device)
Received by server
Wed, 12 Aug 2026 04:52:49 GMT
Time anchor
proven no earlier than Wed, 12 Aug 2026 04:52:30 GMT — drand round 6369311 (unpredictable beacon bound into the proof)
Location
30.88695, 121.93449 ±35m map (claimed by device, radius bound into the proof)
SHA-256
70814041daff5c45ad99b1db182ca6bffd2767a02812368fd27cfad947af1ed0
Poseidon commitment
5377974133836588774858161991421513709976994143585309402815472023749114669782

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

0xc5404331be29000741bede407ae43f34d444253dbfe12ca8d33d0aae76e5b564

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