zkpass-primary-sources-2026-05-14

zkPass primary sources

Reviewed: 2026-05-14 UTC

Core protocol framing

• https://docs.zkpass.org/overview/introduction
  • Defines zkPass as a decentralized oracle protocol that turns private internet data into verifiable proofs onchain using zkTLS.
  • Says the system works with HTTPS websites without requiring OAuth APIs, API keys, or trusted intermediaries.
  • Lists the broad proof domains zkPass targets, including identity, financial, healthcare, social, professional, and digital-asset data.

Technical architecture / whitepaper layer

• https://docs.zkpass.org/overview/technical-whitepaper
  • Describes the four key roles: Prover, Verifier, Node, and DataSource.
  • Frames zkPass as a combination of 3P-TLS, MPC, and interactive zero-knowledge proofs.
  • Useful for understanding the architectural claim that the verifier should learn only the proved statement while the provenance of HTTPS data remains cryptographically anchored.

Developer workflow and proof orchestration

• https://docs.zkpass.org/developer-guides/js-sdk/how-it-works.md
  • Best source for the operational flow: SDK → allocator node → TransGate → data-source login → 3P-TLS among extension, validator node, and data source → proof generation → validator verification → result back to DApp.
  • Makes allocator and validator nodes explicit as separate roles.
• https://docs.zkpass.org/developer-guides/js-sdk/quick-start.md
  • Documents the developer-control layer: DevHub project creation, appid, schema selection, domain matching, immutable schema creation, and JS-SDK launch flow.
  • Also shows proof sessions can optionally bind a wallet address to the result.

Schema and anti-sybil surface

• https://docs.zkpass.org/developer-guides/js-sdk/schema.md
  • Most important source for the schema model itself: intercepted API requests, extraction paths, assertions, and required nullifier.
  • Explicitly says the nullifier is hashed with MPC-generated randomness inside the zk circuit and can be used by developers to prevent sybil attacks.
  • Shows that proof policy is partly encoded in developer-authored schema JSON rather than only in protocol code.

Official project handles and examples

• https://github.com/zkPassOfficial
  • Official GitHub org; concise description says zkPass is built on 3P-TLS and hybrid ZK and is meant to make web private data verifiable.
• https://raw.githubusercontent.com/zkPassOfficial/zkPass-tutorial-examples/main/README.md
  • Shows the practical integration surface: JS-SDK examples, O1JS/Mina verification examples, schema examples, and contract examples.

Governance / token layer surfaced in docs

• https://docs.zkpass.org/get-started.md?ask=What%20governance%20or%20token%20mechanisms%20does%20zkPass%20describe%20for%20its%20network%20or%20DAO%3F
  • The docs’ own retrieval interface summarizes a Swiss-association DAO, ZKP token governance, validator collateral, fee burns, buybacks, and multisig treasury execution.
  • This is useful because it shows zkPass is not only a proving SDK; it also presents itself as a governed network with economic coordination.

Main takeaways from this pass

• zkPass is a schema platform plus node-orchestrated proof network, not merely a generic zkTLS claim.
• The decisive control surfaces are schema authorship, allocator/validator node operation, TransGate distribution, DevHub project/domain policy, and the nullifier design used for uniqueness.
• Compared with lower-layer transcript-proof primitives, zkPass exposes more application-platform structure; compared with higher-layer identity products, it still preserves a reusable middleware layer.
• zkPass is especially valuable in the corpus because it sharpens the difference between raw web-proof cryptography and productized proof orchestration.