zkPass

• zkPass lets users prove facts about their private data from any website without revealing the data itself.

• Its zkTLS technique combines standard web encryption with zero-knowledge proofs, needing no API access or cooperation from the site.

• ZKP is the network token.

• Supply allocated across community, ecosystem and investors.

• Used for proof generation fees and network participation.

Pros:

• Working without site cooperation is the key advantage; API-based verification requires permission that is rarely given.

• Applications in credit, identity and eligibility verification are concrete.

• Users prove specific facts rather than handing over full documents.

Cons:

• Websites can and do implement countermeasures against this class of technique.

• Legal position on extracting verified data from third-party sites without permission is unsettled.

• Proof generation adds friction to the user experience.

• Exposure to private data verification that works without institutional cooperation.

• Sidesteps the API access problem that blocks comparable approaches.

• Weigh the legal and technical countermeasure risks.

• Proving facts from any website using its existing encryption, without needing the site's permission or an API.

• Proving something about your bank balance or account status requires the institution to cooperate, and most will not.

• Deriving the proof from the encrypted session removes the need for their participation.

• Founded by a team operating publicly.

• Backed by Binance Labs, dao5 and Sequoia China.

• No public ICO. Distributed via Binance ecosystem programmes and airdrop in 2025.

• Websites may deploy countermeasures against the technique.

• Legal position on unpermissioned data extraction is unsettled.

• Proof generation friction limits mainstream use.

• Competition from other zkTLS implementations.