What is zkPass (ZKP)?
Quick Facts
- Token symbol: ZKP
- Token standard: ERC-20, also deployed on BNB Smart Chain and Base
- Core technology: Zero-Knowledge Proofs (ZKP), Multi-Party Computation (MPC), and 3P-TLS
- Main product: TransGate browser extension
- Key utility: Validator staking, governance, settlement, and service access
- Funding: $12.5 million Series A at a $100 million valuation
- Token allocation: 48.5% community, 10% DAO treasury
Introduction
zkPass is a privacy-preserving data verification protocol that bridges the gap between Web2 and Web3. It allows users to prove specific facts about their private data — such as identity, credit score, or account balances — without ever uploading or revealing that data to any third party.
The protocol is built on three core technologies: Zero-Knowledge Proofs (ZKP), Multi-Party Computation (MPC), and a redesigned three-party TLS connection known as 3P-TLS. Together, these tools make it possible to verify real-world information on-chain in a completely privacy-respecting way.
History & Background
zkPass was inspired by the academic vision of a 'Decentralized Society' — a future where identity and credentials are controlled by individuals rather than centralized platforms. The team raised a $12.5 million Series A funding round in 2024, reaching a valuation of $100 million, reflecting strong institutional confidence in the protocol's approach.
The ZKP token's official tokenomics were announced in late 2025, marking a key milestone in the protocol's transition toward a fully community-governed ecosystem.
How zkPass Works
At the heart of zkPass is the TransGate browser extension. Users install TransGate, log into any standard HTTPS website, and select data fields they want to verify. The extension then generates a cryptographic zero-knowledge proof of those data attributes directly on-device.
The 3P-TLS protocol adds a decentralized MPC node as a third party to the standard TLS handshake. This node verifies data integrity and authenticity using only a share of the MAC key — critically, the encryption key never leaves the user's device, so raw data is never exposed.
Verified results can be delivered to any supported blockchain — Ethereum, BNB Chain, Solana, TON — or even off-chain, making zkPass chain-agnostic by design.
Tokenomics
The ZKP token is the native utility token of the zkPass ecosystem. It serves multiple functions: acting as a settlement medium, providing validator collateral for MPC node operators, enabling access to protocol services, and powering governance through the DAO.
Token distribution prioritizes community ownership, with 48.5% allocated to the community and 10% to the DAO treasury. Early investors and core contributors receive their allocations on long lock-up and vesting schedules, aligning long-term incentives with protocol growth. A small liquidity allocation was fully unlocked at the Token Generation Event (TGE).
|
Circulating supply
| 274.68 million ZKP |
|---|---|
| |
|
Total supply
| 1.00 billion ZKP |
|
Max supply
| -- ZKP |
Ecosystem & Use Cases
zkPass enables a wide range of real-world verification use cases:
- KYC and identity verification without uploading personal documents
- Credit scoring using private financial data from Web2 platforms
- Airdrop eligibility checks that protect user privacy
- Membership and access control for DApps requiring verified credentials
Developers can integrate zkPass into their applications using the open-source TransGate SDK, which requires no OAuth API or special licensing from the data source.
Team, Governance & Community
zkPass is governed progressively through a DAO structure, with the ZKP token enabling holders to vote on protocol upgrades and ecosystem direction. The DAO treasury, funded with 10% of the total token supply, supports ongoing development and community initiatives. Core contributors operate under long vesting schedules to ensure sustained commitment.
Advantages
- True data privacy: Raw data never leaves the user's device or browser at any point
- Universal compatibility: Works with any HTTPS website, no API integration needed
- Chain-agnostic: Proofs can be delivered on-chain or off-chain across multiple networks
- Anti-cheating: Decentralized MPC nodes prevent data tampering by any single party
- Developer-friendly: Open-source TransGate SDK simplifies DApp integration
Risks & Challenges
- Technical complexity: MPC and ZKP technology requires significant compute and engineering expertise
- Adoption hurdles: Requires users to install the TransGate browser extension, adding friction
- Regulatory uncertainty: Privacy-preserving identity tools may attract scrutiny from regulators
- Token vesting pressure: Large future unlock events could create sell pressure over time
- Competitive landscape: Other zkTLS and identity verification protocols are emerging rapidly
Long-Term Vision
zkPass aims to become the foundational identity infrastructure for the decentralized internet, enabling both humans and AI agents to prove verifiable facts about themselves without sacrificing privacy. By turning any HTTPS data source into a verifiable credential layer, the protocol aspires to create a trustless, privacy-first standard for identity, reputation, and data portability across Web3.
Frequently Asked Questions
- What is zkPass?
zkPass is a privacy-preserving protocol that allows users to verify private Web2 data on-chain without revealing the underlying information. It uses a combination of Zero-Knowledge Proofs, Multi-Party Computation, and a three-party TLS protocol.
- What is the ZKP token used for?
ZKP is the native utility token of the zkPass ecosystem. It is used for validator staking to secure the network, as a settlement medium, for governance participation through the DAO, and to access protocol services.
- What is TransGate?
TransGate is a browser extension developed by zkPass that allows users to authenticate data from any HTTPS website and generate a zero-knowledge proof without uploading any personal information. Developers can also integrate it into their DApps via the open-source TransGate SDK.
- How does zkPass protect user privacy?
zkPass uses MPC nodes to verify data integrity without ever accessing the user's raw data. The encryption key always stays on the user's device, and zero-knowledge proofs allow verification of data attributes without revealing the actual content.
- What blockchains does zkPass support?
zkPass is chain-agnostic and can deliver verified proofs on Ethereum, BNB Chain, Solana, TON, or entirely off-chain. The ZKP token is also deployed on BNB Smart Chain and Base.
- What are the main use cases for zkPass?
zkPass supports identity verification (KYC), credit scoring, airdrop eligibility checks, and DApp access control. These use cases all benefit from the ability to prove verified facts about private data without disclosing it.
- How was zkPass funded?
zkPass raised a $12.5 million Series A funding round in 2024, at a valuation of $100 million. This round reflected institutional confidence in the protocol's zero-knowledge and MPC-based approach to privacy-preserving identity.
- How is the ZKP token distributed?
The largest portion (48.5%) is allocated to the community, with 10% going to the DAO treasury. Early investors receive 22.5% under long lock-up and vesting schedules, and core contributors receive 14% with extended vesting to align long-term incentives.