Why does the TLSNotary extension ask to "read and change all your data on all websites"? Because that's what proving real HTTPS traffic in the browser takes. What keeps it safe: sandboxed plugins, declared scopes, runtime checks, and per-proof approval.
tlsnotary.org/blog/2026/06/1…
We're close to releasing a TLSNotary Android app, but Google requires a round of closed testing before we can publish it.
Got an Android device and want to help? DM us your Gmail and we'll add you to the test:
play.google.com/apps/testing…
iPhone users can help too! You can try the app right now via TestFlight:
testflight.apple.com/join/7Y…
TLSNotary v0.1.0-alpha.15 is out.
TLSNotary now supports proxy mode alongside MPC mode: a faster, lighter alternative when the security tradeoff fits your use case.
Also: chunked HTTP responses, an SDK core refactor, no-OS-RNG verifier builds.
github.com/tlsnotary/tlsn/re…
Want to see what proxy mode actually feels like?
Try it in your browser:
demo.tlsnotary.org/#mode-com…
New post: the full-reveal fast path.
When the prover is going to share the response in full anyway, we skip ZK-proving it and hand the verifier the session write key instead. Much faster, if your use case fits.
Read more at tlsnotary.org/blog/2026/05/1…
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.
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 👇
pse.dev/blog/introducing-spe…
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.
tlsnotary.org/blog/2026/05/1…
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.
tlsnotary.org/blog/2026/04/2…
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.org/blog/2026/01/1…
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.
We’re sunsetting the @PrivacyEthereum-hosted notary servers at notary.pse.dev on March 18.
It was always intended for development and testing. If you’re building with it, please plan to self-host.
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?
fosdem.org/2026/schedule/eve…
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: tlsnotary.org/blog/2026/01/3…
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: youtube.com/playlist?list=PL…
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: calendar.google.com/calendar…






