TLSNotary
@tlsnotary
Export data from any web application and prove facts about it without compromising on privacy.
2 Following 1.3K Followers
SpeakUp is built for exactly the setting TLSNotary operates in: a low-power device running the prover, online with a designated verifier. A fast client-side zkVM is the missing piece for scaling web proofs.
Show more
SpeakUp: a new zkVM we're prototyping for private, client-side proving of WebAssembly programs - built to run on low power devices such as mobile phones and browsers.
The underlying proof system explore different tradeoffs for different use cases from mainstream zkVMs. SpeakUp is interactive, and uses vector oblivious linear evaluation (VOLE), which provides a fast linear-time prover and post-quantum security at the cost of larger proofs.
See the early design draft below, we're looking for public feedback 👇
Show more
We benchmarked the upcoming Proxy mode against MPC across cable, 5G, and fiber for both native and browser. As expected, Proxy is faster. Proxy finishes a 1KB/2KB attestation in 1–2s vs 3–15s for MPC.
Show more
New mode coming to TLSNotary: Proxy Mode.
Verifier proxies TLS, prover sends a ZK proof after the session. Much lower bandwidth than MPC-TLS, but with a network-path trust assumption.
MPC-TLS stays the default. Opt in when it fits.
Show more
Who's your #1# Spotify artist?
Prove it onchain. We pay the gas.
We’ve updated the performance numbers in the alpha.14 blog post after fixing an issue in the benchmark harness.
Good news: the numbers look even better now 📈
TLSnotary is one of the most important AI projects out there, but you’re not ready to have that conversation.
(use it to move your memory.md files across LLMs)
kudos to @sinu_eth, @AndyGuzmanEth & the EF privacy team for bringing it to life and making it FOSS.
Show more
We’re sunsetting the @PrivacyEthereum-hosted notary servers at on March 18.
It was always intended for development and testing. If you’re building with it, please plan to self-host.
Show more
The recording of our @fosdem talk “Liberate Your User Data with zkTLS: Verifiable HTTPS Using TLSNotary” by @heeckhau is now available.
How can users generate cryptographic proofs from HTTPS without server changes?
Show more
How do you benchmark MPC-TLS under realistic network conditions (and in real browsers)?
We wrote up how TLSNotary’s reproducible testing/benchmark harness works:
If you’re exploring zkTLS or verifiable web data, this is worth your time.
At Devconnect, we hosted a full zkTLS Day with talks from across the ecosystem.
All recordings are here:
Show more
Missed our TLSNotary Office Hours this morning? No worries: we run them every 2 weeks
Open session for questions, feedback, or help building with TLSNotary.
Subscribe to the calendar so you don’t miss the next one:
Show more
Our tech lead @sinu_eth blogged about why #zkTLS# is the missing primitive for @ethereum, unlocking universal data portability and selective disclosure for the internet.
Show more
After years of attending @fosdem, I’m finally stepping on stage.
Join me on Sunday, Feb February 1 in Brussels in the Decentralized Internet & and Privacy devroom for a talk on Verifiable HTTPS using TLSNotary
Show more
@tlsnotary v0.1.0-alpha.14 has been released.
This version focuses on usability improvements and brings more performance gains, particularly for WASM targets.
TLSNotary: the universal API
We made it possible.
In 2026 we make it easy.
(Image from
When will someone use TLSN to vampire attack fintech?
Current playbook is simple: trap users with their own data.
Spend years building credit history with a bank. That data unlocks better rates, higher limits, real value.
Switching means starting from scratch.
New institutions can’t verify your claims. Documents are forgeable.
Your bank won’t share with competitors.
TLSNotary breaks this trap.
Zero-knowledge proofs let you prove financial history to new institutions without:
∙Sharing login credentials
∙Your bank knowing
∙Any Open Banking integration
Show more
