CAPTURE PROOF
zkShot capture
Session-boundBeacon-anchored earliest timeCamera not attested
Capture details⌄
Capture time
Tue, 11 Aug 2026 14:35:26 GMT (claimed by device)
Received by server
Tue, 11 Aug 2026 14:35:27 GMT
Time anchor
proven no earlier than Tue, 11 Aug 2026 14:35:00 GMT — drand round 6367596 (unpredictable beacon bound into the proof)
Location
not shared
SHA-256
bc7e239abbfbda8edd81b5a1985fddd712969ad72a4adcda8eee28bd9321d55c
Poseidon commitment
20867735080328859397994292241141235183499125863580326775532624560826583973837

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

0xe8bfac0588326001c7aa3d38733760226d67e4eaabf04388d633e99bcf6eb24b

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)