Comment on page

Overall Architecture


zkPass primarily employs technologies such as Three-Party TLS (3P-TLS), Multi-party Secure Computation (MPC), and Zero-Knowledge Proof (ZKP). These technologies enable provers to convert any private data from HTTPS websites into zk proofs. At the same time, they ensure privacy protection and prevent data forgery by malicious users.

Data Layer

This describes the various types of data sources that the zkPass Protocol is capable of handling, including public on-chain data and any off-chain private data secured by HTTPS. The zkPass Protocol then generates identity credentials by processing data according to the data persistence protocol and homomorphic encryption data lake standard.

Protocol Layer

Contains the most important three sub-protocol modules implemented by zkPass Protocol, namely
Oblivious TLS Protocol: implements an efficient 3-party TLS protocol, and supports both CBC and GCM block cipher modes;
MPC Protocol: implements a data exchange protocol with low communication cost and encapsulates it as a component to provide external privacy computing services;
ZKP Protocol: implements a memory-friendly zero-knowledge proof protocol, and provides two API methods to empower the Web3 privacy ecosystem.

Network Layer

Contains the blockchain network that zkPass Protocol can support, and the main contract modules involved in the protocol, which are
Task: task distribution smart contract;
Template: support data source smart contracts;
ZK-Verification: Zero-knowledge verification of smart contracts.

Identity Layer

Authenticated users will end up with a series of sovereign data, including
zkSBT: represents participation in certain types of identity authentication activities and ZK proof for privacy verification;
typeSBT: represents a certain type of identity authentication activities participated in;
dateSBT: represents that the identity comes from a trusted data source;
mainClaim: represents the main claim about the identity;
queryClaim: represents the secondary claim included in mainClaim.

Product Layer

The user's sovereign data represents various identities in the Web3 ecosystem, which can be applied across different Web3 and Web2 application scenarios.
Integrating or building on top of the zkPass Protocol, zkPass Products with unique features will be developed to adapt to specific application scenarios.
Feel free to contact us if you have any ideas