zkPass Technology Overview: A Privacy-Focused Oracle Protocol

Introduction to zkPass

zkPass is an innovative oracle protocol designed to enable privacy-preserving, on-chain verification of internet data. Built on zkTLS technology—a combination of 3P-TLS and Hybrid ZK protocols—zkPass allows users to securely share sensitive data (e.g., legal identity, financial records, educational credentials) without exposing personal information. Its applications span AI, decentralized identity (DID), lending, and beyond.

Key Features

• Privacy-Centric Design: Users control data sharing via zero-knowledge proofs (ZKPs), ensuring no raw data leaves their device.
• Universal HTTPS Compatibility: Works with any HTTPS website without requiring OAuth API integration.
• Multi-Industry Use Cases: Supports DeFi, healthcare, education, and more by verifying data authenticity while preserving privacy.

Core Technology Stack

1. zkTLS: The Foundation

zkTLS integrates three core components:

1. 3P-TLS Protocol: Extends traditional TLS to a three-party model (user, verifier, data source).
2. MPC (Multi-Party Computation): Securely generates encryption/MAC keys without full exposure to any single party.
3. Hybrid ZK Proofs: Combines interactive (VOLE-ZK) and non-interactive (SNARK) proofs for efficiency and flexibility.

How 3P-TLS Works

• Phase 1 – Tripartite Handshake: Generates session keys split between user (P), zkPass node (V), and data source (S).
• Phase 2 – MPC-Based Key Exchange: Computes enc_key (held by user) and mac_key (split between user/node) to ensure data integrity.
• Phase 3 – Standard TLS: Secures application data flow, followed by ZKP preparation.

👉 Learn how zkTLS enhances data privacy in Web3

2. Hybrid Zero-Knowledge Proofs

zkPass employs a two-tier ZKP system:

Interactive ZK (VOLE-ZK 23)

• Purpose: Authenticates data origin and prevents tampering.

• Process:

  1. User and node co-generate VOLE instances (m = k + w * delta).
  2. User commits to circuit satisfiability via linear relations (optimized for AND gates).
  3. Verifier checks consistency using VOLE parameters.
• Optimizations: SoftSpoken OT reduces network overhead by 50%; AES128 proofs cut block counts by 300x.

Non-Interactive ZK (SNARK)

• Purpose: Enables public verification with selective disclosure.
• Implementation: Uses Circom to convert IZK results into Merkle tree-based proofs verifiable on-chain.

zkSBT: Secure Data Attestation

zkPass introduces zkSBTs (Zero-Knowledge Soulbound Tokens) to manage credentials:

• tSBT: Represents data categories (e.g., legal identity, financial records).

• dSBT: Stores actual credentials (e.g., government-issued ID) with:

  • Master Claims: Raw data hashes (stored privately).
  • Query Claims: ZK-verified assertions (e.g., "age > 18").

flowchart LR
    User -->|MPC| dSBT -->|ZK Proof| Verifier
    dSBT -->|Merkle Root| SmartContract

Security Model

zkPass mitigates threats through:

1. Gateway Protection: Masks client identities via TLS randomness.
2. Fisherman Nodes: Randomly audit verifiers to detect malice (reward/punish via staking).
3. Automated Arbitration: Mediators replay VOLE parameters to resolve disputes.

"The protocol ensures nodes cannot access user data, while clients cannot forge proofs." — zkPass Whitepaper

FAQs

Q1: How does zkPass differ from traditional oracles?

A: Unlike Chainlink or Band Protocol, zkPass verifies HTTPS data without exposing raw data or relying on centralized APIs.

Q2: Is zkPass compatible with all websites?

A: Yes, any site supporting HTTPS/TLS can be integrated—no backend changes required.

Q3: What’s the performance impact of ZKP generation?

A: Optimizations like SoftSpoken OT reduce proof generation time by 3x vs. baseline MPC.

Q4: How are credentials stored?

A: Data remains on-user-device; only ZK proofs and hashes are shared.

Conclusion

zkPass redefines trusted data sharing by combining TLS, MPC, and hybrid ZKPs. Its architecture prioritizes privacy, scalability, and cross-industry applicability—making it a pivotal solution for Web3’s data verification challenges.

👉 Explore zkPass use cases in decentralized finance

Official Resources:
Website | GitHub | Whitepaper