It's great to see zkTLS being highlighted as a powerful solution for privacy-preserving data verification.

We appreciate how @0xLTR from @Delphi_Digital showcased zkPass and other projects driving this innovation, proving that secure, verifiable data without exposing sensitive information is a key step toward a more trustworthy internet.

The Internet's proof system is broken. We overshare personal information to verify the smallest claims.

zkTLS allows you to verify everything while exposing nothing. Here are three projects making this happen.
@reclaimprotocol transforms any Web2 data into cryptographic proofs for Web3. Pick a data source and enter credentials in their secure form.

Reclaim's proxy attestor converts the web request into proofs. Your device then runs a zkSNARK to extract just what you need to prove, hiding everything else.
You can prove your social following without sharing your handle or verify income without exposing transactions. Proof generation can be done in under 4 seconds.

@zkPass aims for a similar goal, but bets on adaptability over simplicity.

zkPass specializes in private data verification with its hybrid Three-party TLS system, which combines MPC and proxy-based models, adapting to changing network conditions and server requirements on the fly.

When you want to prove something, ZKPass creates a TLS session either via their decentralized MPC network or a direct proxy, depending on the scenario.

You can prove data from essentially any site, not just specific providers. The MPC portion ensures no single node can forge a session to maintain security.

ZKPass has already been utilized in private credit scoring, financial transactions, and online voting. By not boxing themselves into one model, they've proven you can mix and match proxy/MPC to meet different client needs.

@onflowxyz is a newcomer offering a "ZK on-chain passport" solution.

By creating attestable identities called "Sundial passports," Onflow allows you to KYC once and satisfy future checks with one click.

By running processes locally, verifiers and protocols learn nothing beyond the proof they need to verify the user.

Unlike Reclaim and zkPass which prove any data, Onflow focuses on identity verification.

zkTLS isn’t coming. It’s already here.