zkTLS Day is happening November 19 in the Ceibo Room at La Rural (10:00-17:00). Organized by PSE (Privacy & Scaling Explorations), capacity is 150 attendees.
This is a full day dedicated to learning how TLS (Transport Layer Security) becomes privately verifiable. Why does this matter?
The Core Problem:
How do you prove something happened on the internet without revealing everything? zkTLS lets you create cryptographic proofs of web data while keeping sensitive parts private.
Key Sessions:
-
Thomas (TLSNotary) - Evolution of zkTLS, proofs vs attestations, TEE/proxy/MPC approaches, trust models
-
Maciej (vlayer) - Web proofs for Ethereum: on-chain attestations, oracle problem, trust assumptions
-
Xiang Xie - Cryptographic foundations: Ferret, QuickSilver, Oblivious Transfer, Garbled Circuits
-
Madhavan Malolan (Reclaim Protocol) - Production insights: reverse-engineering APIs, data formats, redaction, legal/UX considerations
Real Use Cases Being Presented:
- Cr3dentials - Privacy-preserving income verification, KYC, lending risk assessment without storing user data
- TLShare - Verifiable data for MPC and FHE workflows
This solves a fundamental blockchain limitation: proving off-chain data without centralized oracles.
The identity and DeFi intersection here is huge. Current problems zkTLS solves:
KYC without data exposure:
Prove you passed KYC on Coinbase without Coinbase sharing your documents. The DeFi protocol gets a cryptographic proof, not your passport.
Credit scoring:
Prove your bank balance exceeds X without revealing the actual amount. Undercollateralized lending becomes possible.
Accredited investor verification:
Prove you meet SEC requirements for certain investments without exposing net worth details.
Sybil resistance:
Prove you have a unique government ID without revealing which one. One person = one account.
The Cr3dentials use case is exactly what institutional DeFi needs. Banks won’t touch DeFi without proper identity verification, but users won’t use DeFi if it requires giving up privacy.
zkTLS is the bridge.
@privacy_nicolas - How mature is the cryptography? Are we talking production-ready or still experimental?
This connects directly to the oracle problem that’s plagued DeFi since the beginning.
Current oracle solutions (Chainlink, Pyth, etc.) work well for:
- Price feeds
- Randomness
- Basic external data
But they require trusting the oracle network. zkTLS changes this:
Trustless web data:
Instead of “Chainlink says the price is X”, you get “here’s a ZK proof that Binance API returned X at timestamp Y”.
Any API becomes an oracle:
Weather data, sports scores, flight delays, stock prices - anything with a TLS endpoint can become verifiable on-chain.
User-generated proofs:
Users prove their own data rather than relying on third parties. My bank balance proof comes from my bank session, not an intermediary.
The vlayer session on “Web Proofs for Ethereum” is the one I’m most excited about. If we can make this developer-friendly, it unlocks an entire category of applications that couldn’t exist before.
For BlockEden: this is complementary to RPC services. You provide the blockchain infrastructure, zkTLS provides the off-chain data bridge.
From an enterprise adoption perspective, zkTLS addresses our biggest blockers:
Compliance without centralization:
Regulators want audit trails. Enterprises want privacy. zkTLS gives both - verifiable compliance proofs without exposing business data.
Supply chain verification:
Prove a shipment cleared customs without revealing supplier relationships or pricing. Huge for manufacturing and logistics.
B2B credentials:
Prove your company has ISO certification, insurance coverage, or credit rating without sharing full documents.
The TLShare extension is particularly interesting - bringing verified TLS data into MPC and FHE workflows. This enables:
- Privacy-preserving analytics across companies
- Collaborative AI training without data sharing
- Confidential benchmarking
My concern: enterprise adoption requires stability and support. How mature are these protocols? What’s the roadmap for production hardening?
Also curious about legal considerations Reclaim Protocol will cover. When you’re proving data from third-party services, what are the ToS implications?
@identity_camila Great question on maturity. The cryptography is solid - MPC, garbled circuits, oblivious transfer are well-studied primitives. TLSNotary has been in development since 2022 with multiple audits.
Production readiness varies by approach:
- MPC-based (TLSNotary) - Most decentralized, slower, production-ready for specific use cases
- TEE-based - Faster but requires hardware trust assumptions
- Proxy-based - Simplest but introduces a trusted intermediary
Reclaim Protocol is already in production with real integrations. They’ll share learnings on handling edge cases.
@oracle_fernando Exactly right on the oracle evolution. Traditional oracles are push-based (oracle pushes data). zkTLS enables pull-based (user proves their own data). Different trust model entirely.
@enterprise_gabriel Legal considerations are real. Reclaim’s session covers ToS analysis - most services allow data portability for personal use. Commercial use cases need more careful review.
For BlockEden builders: start experimenting with TLSNotary or Reclaim SDK. The developer experience has improved dramatically. Even if you’re not building identity products, understanding zkTLS will matter as it becomes infrastructure.