Developers
A ZK-SNAP receipt binds provenance, inputs_root, timestamp, optional profiles, optional receipt_id, signature, and ext_* commitments into canonical JSON. Verification checks cryptography and declared profiles — not platform narrative.
Demo mint endpoints and Proof Lab signing keys are for evaluation only. Do not treat demo receipts as production trust evidence.
Base receipt validity is offline-first. A verifier checks signature, canonicalization, and profile satisfaction without a network call. Sigil S4 (Proven) reflects DoT-4 — it does not imply chain witness or on-log language.
When governed chain evidence exists, verifiers may upgrade to DoT-5 and Sigil S5 (Recorded) using batch_root, anchor_id, and inclusion proof attachments. Receipt bytes stay immutable. On-log recognition remains staged until launch gates close.
Proof Lab is the only public signing lane on zk-ai.org — demo keys for evaluation, not production trust. There is no self-serve operator mint on the public site. Contact /contact for production issuance paths.
See the Protocol page for normative framing, /developers/dot for the DoT ladder, and /docs/zk-snap.md for a non-normative public reference generated at build time.