Same image, same receipt
The fingerprint matches and the signature verifies. The production event is unchanged. ZKAI™·S4 Proven.
Proof Lab
Create, Edit, Verify.
Files move. Metadata disappears. Edits blur what actually happened. Proof Lab shows why receipts matter: the original production event stays checkable after the file leaves its platform. When the image changes, the match fails clearly — no dashboard, no guesswork, no trust-me record.
Your image never leaves this browser Receipt signed at the moment you create it Proof fails the instant you change the file
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.
No receipt yet. Select an image, then create a receipt.
Receipt created
Status—
Artifact—
Mode—
Issuer key—
Receipt ID—
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
- —
What This Proves
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.
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.
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.