Zero-Knowledge Compliance

Compliance Proof Example

Illustrative pseudocode: users generate ZK proofs to satisfy verifier requirements without revealing private data. The normative interfaces are defined in the specification.

// User wants to deposit to a compliant exchange
// Exchange requires: KYC + sanctions clearance

// 1. User already holds credentials from trusted issuers
const credentials = client.listCredentials({
  types: ["zkc:cred:kyc:v1", "zkc:cred:sanctions:v2"],
  notExpired: true
});

// 2. Exchange signs an Authenticated Proof Request (APR)
const request = {
  requirements: {
    proofTypes: ["zkc:proof:kyc:v2", "zkc:proof:sanctions:v8"],
    parameters: {
      "zkc:proof:kyc:v2": { minLevel: "enhanced" },
      "zkc:proof:sanctions:v8": {
        canonicalSet: [100, 200],
        setRoot: "0x2dd2eee7fc84e095b925d9a97a60a1ad3647661c51935f61d4c3dacbff4ec3ec"
      }
    },
    maxProofAge: Duration.hours(24),
    context: {
      profile: "zkc:context:purpose-bound:v1",
      value: purposeBoundContext,
      purpose: "exchange deposit eligibility"
    }
  },
  trustPolicy: exchange.trustPolicy
};
const apr = {
  request,
  verifierId: exchange.id,
  nonce,
  issuedAt,
  expiresAt,
  signature: exchangeSignature
};

// 3. The holder SDK validates the APR signature, expiry, nonce, and
// purpose-bound context, then records separate consent for each atomic
// predicate before calling the canonical generation interface.
const proof = await client.generateProof(apr.request, credentials);
// Proves: valid KYC + clear sanctions screening
// Hides: name, address, DOB, specific issuer, credential ID
// Default presentation: zkc:presentation:anonymous:v1

// 4. The verifier validates the same signed APR and proof (~15ms)
const result = await verifyComplianceProof(exchange, proof, apr.request, apr);
// result.valid === true

// 5. The holder retains a Disclosure Receipt for the signed request

The exchange learns only that the user meets requirements. No personal data crosses the wire.