zkShotCAPTURE PROOF
zkShot capture
Capture details
Capture time
Mon, 10 Aug 2026 18:07:02 GMT (claimed by device)
Received by server
Mon, 10 Aug 2026 18:07:05 GMT
Location
not shared
SHA-256
2427289788843eb955e96ff4e53302a04450eaef56f392e2657fb64f9ca4b3be
Poseidon commitment
740599552250791278418816363186014624159353606870709172334370721361516281349

zkVerify verification

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

0x6f54007d0668288bd752d0cb47c261f5f334f795bfa7c446c6c0bf2a5c31ea36

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.