QuantZK Documentation
Verifiable Decision Infrastructure (VDI): cryptographic receipts any verifier can check offline.
Start here (billing wedge)
- Quick Start —
quantzk.billing.attest+verifyin minutes - API billing pilot — two HTTP calls (
/attest+/verify) - API billing production — keys, migrations, Phase-2 binding
- API Reference — billing attest/verify + auditor endpoints
- Live demo — quantzk.com/vdi-billing
- Revocation feed — api.quantzk.com/.well-known/vdi-billing-revocation.json
- Browser verifier —
/protocol/verify.html(no issuer UI)
What is QuantZK?
Open protocol for machine-checkable decisions. Issue a signed attestation; verify with math, not log exports. No QuantZK servers required for verification.
Who is this for?
- AI/ML Engineers, Prove your model followed fairness constraints without exposing weights
- Compliance Teams, Review cryptographic evidence that encoded policy checks passed
- Agent Developers, Build trust between autonomous agents without shared state
- Platform Engineers, Add verifiable decision audit trails to any system
- Regulators, Receive independently verifiable proofs instead of self-reported logs
Core Concepts
| Concept | What it does |
|---|---|
| Decision Attestation | A signed, portable proof that a decision followed rules |
| Verification | 7-step offline check using Groth16 ZK proofs + Ed25519 signatures |
| Verification Receipt | A signed record that verification occurred, enables trust propagation |
| Trusted Verifier Set | A k-of-n quorum policy for accepting receipts |
| Verification Profile | Semantic agreement on what "verified" means (strict, standard, minimal) |
| Transparency Log | Append-only log that detects verifier equivocation |
| Policy Manifest | A versioned, hashed set of constraints (e.g., Fair Lending, HIPAA) |
Documentation
| Guide | Description |
|---|---|
| Quick Start | Billing attest + verify in minutes |
| API billing pilot | Local two-call integration runbook + pilot surface table |
| Billing pilot tests | Canonical test:billing-pilot command (15/15) |
| External validation packet | Reviewer index — PRs, tests, hashes, deliverables |
| Operational readiness | Pilot packet CI gate + perf budget summary |
| apiBillingV2 trusted setup | MPC ceremony + artifact rotation (pre-adversarial trust) |
| API billing production | Production deploy, env, Phase-2 |
| Core Concepts | Deep dive on attestations, receipts, trust |
| API Reference | Full API for all packages |
| Enterprise Workflows | Lending, clinical, autonomous agent examples |
| Trust Model | Receipts, TVS, profiles, transparency |
| Security Model | Threat model, circuit governance |
| FAQ | Common questions answered |
Quick Links
- Protocol Specification (VDI-SPEC.md)
- Architecture Diagrams (ARCHITECTURE.md)
- Source repository — available on request (Omar@quantzk.com)
The Key Commitment
If QuantZK disappeared tomorrow, attestations issued with embedded verification keys would still verify with the open-source verifier and pinned artifacts — subject to profile, revocation, and artifact availability assumptions.
Verification keys are embedded in attestations. The verifier is open source. The math doesn't change. This is infrastructure, not SaaS.