Proof Lab

Create, Edit, Verify.

Take any image. ZK-AI signs a receipt at the moment of production. Change the image. Verify again. The proof fails — because the original production event is preserved in the receipt and the edit is immediately visible. That is the protocol working.

Your image never leaves this browser Receipt signed at the moment you create it Proof fails the instant you change the file

Demo boundary

Proof Lab is demo-only. It creates browser-demo S4 receipts with a dedicated demo signing key. It is not a protocol service, not a testnet endpoint, not ZK-AI Chain, not the canonical Evidence Graph, and not a settlement surface.

What This Proves

Same image, same receipt

The fingerprint matches and the signature verifies. The production event is unchanged. ZKAI™·S4 Proven.

Changed image

The receipt is still signed — but the production event changed. The receipt no longer belongs to this file.

Changed receipt

The signature check fails. The production memory was tampered with after signing.

Create

Create receipt

The image stays in your browser. ZK-AI receives only the fingerprint needed to create the demo receipt.

Image preview No image selected.
File
Waiting for image
Size
-
Type
-
Fingerprint
Not made yet

No receipt yet. Select an image, then create a receipt.

Verify

Verify receipt

Select your edited image to see the mismatch, or the original to see it pass. ZK-AI checks the fingerprint against the signed receipt.

Original fingerprint
Verify fingerprint
Technical details Claim and receipt JSON for developers. Normal verification starts from the image or file.

Field names in saved JSON may include machine-readable keys used by the Protocol Implementation. This area is for inspection and advanced workflows.

Next step

Read the ZK-SNAP specification.

Proof Lab shows local create and verify. The Protocol page defines the receipt format, chain anchoring, Sigils, and conformance — the full ZK-AI reference model.