zkPass allows to unlock web2 data for web3 applications, with privacy. Scroll down to get the full technical deep dive.
What is zkPass?
zkPass is a protocol that uses Zero-Knowledge proofs to let you prove facts about your private Web2 data (from any HTTPS website) to Web3 applications. You can verify your identity, reputation, or other attributes without revealing the actual data, keeping your privacy intact. It acts as a privacy-preserving bridge between the walled gardens of Web2 and the open world of Web3.
How It Works: The 3‑Party TLS Protocol
1. Prover (You)
The ‘TransGate‘ browser extension, acting on your behalf to initiate the data request.
2. Verifier (Notary)
A zkPass node that participates in the TLS session to attest to the validity of the data.
3. Server (Website)
The Web2 data source (e.g., your bank, social media) that requires no modification.
Two Modes of Operation
Proxy Mode
The Verifier acts as a proxy between you and the server. It’s fast and efficient.
Pro: Efficient Con: CensorableMPC Mode
You and the Verifier use Multi-Party Computation (MPC) to jointly access the server. It’s slower but cannot be blocked.
Pro: Censorship-Resistant Con: High OverheadzkPass uses a Hybrid Model: it defaults to fast Proxy Mode and automatically switches to MPC Mode if censorship is detected.
Key Use Cases
Private KYC for DeFi
Vampire Attacks
Data Markets
Gaming Achievements
Limitations & Trust Issues
- Centralization: The Verifier node is operated solely by zkPass. You must trust them not to censor you or collude with the prover.
- Privacy: The ‘TransGate‘ browser extension is closed-source. You must trust it not to log or misuse your private session data.
- Trust Assumption: The ZK-Proof only proves that the Verifier correctly checked the data, not that the data itself is true. Public verifiers must trust the Verifier’s integrity.
Get the full PDF report delivered to your inbox: