zkShotCAPTURE PROOF
zkShot capture
Capture details
Capture time
Mon, 10 Aug 2026 18:34:15 GMT (claimed by device)
Received by server
Mon, 10 Aug 2026 18:34:17 GMT
Location
40.73543, -74.00496 map (claimed by device)
SHA-256
77769e87a553fadd2dc82a4b3e393f36db96b87c91a090950a21226fd6bf2275
Poseidon commitment
18389934224363083068363168958358004809894367780423692344859083550834664983842

zkVerify verification

Re-hashing image in your browser…
  1. Queued
  2. Valid
  3. Submitted
  4. IncludedInBlock
  5. Finalized
transaction

0x27aab6d743b1074c36399808d4abeab936dcd88eb8e19e696ccaac8ea7900a52

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 a device commitment together at proving time inside the zkShot capture flow. 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.