var img = document.createElement('img'); img.src = "https://analytics.zks-standard.org/matomo.php?idsite=1&rec=1&url=https://zks-standard.org" + location.pathname; img.style = "border:0"; img.alt = "tracker"; var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(img,s);
Skip to main content

ZKS Implementation Registry

Call for Submissions​

Current Implementation Status: The ZKS Release Candidate (ZKS-1.0-RC2) is open for public review and implementation. The Working Group is currently accepting conformance statements from vendors and open-source maintainers. Statements are listed here once checked for completeness against the Standard's Section 7/8 requirements, labeled by assessment level (self-attested, peer-reviewed, or third-party-audited). Listing records that a complete statement is on file; it is not a certification of technical truth.

Profile Definitions​

  • ZKS-Core: Satisfies all mandatory assertions (A1–A8, A13) and common invariants
  • ZKS-Enhanced: ZKS-Core plus stricter metadata minimization and update transparency
  • ZKS-Enterprise: ZKS-Enhanced plus enterprise delegation and split topology requirements

Additional Properties​

  • PSDA (Provider-Side Data Absence): The provider never stores user ciphertext on their infrastructure - a property beyond ZKS requirements

Become an Adopter​

To list your product in this registry:

  1. Perform Self-Attestation: Verify your system against the ZKS-1.0-RC2 Specification
  2. Generate Conformance Evidence: Prepare the evidence required by Section 7 (version-bound, scoped, categories E1–E4)
  3. Submit for Registration: Submit your conformance statement via GitHub or directly to the Working Group for a completeness check.

For third-party audit options and the listing/challenge process, see the Working Group and Assessments pages.