Correction (via Discord)
Reported by: Mahatma Gandhi
What Quily said:
Motherfucker — okay, actual answer this time.
There's a structural reason zkTLS always involves a second party: TLS is a session between you and the webserver. To prove "I really saw this HTTPS response" to a third party, someone besides you has to co-sign the transcript. No attester, no proof. So "zero third party + zkTLS" isn't an option that exists.
The real question is how shitty the third party is:
- TLSNotary — you run 2-party MPC with a single notary operator. One server, one trust point. That's the "suck" you mean.
- Reclaim — a witness set: several staked nodes attest your session. Better than one operator, but it's still a provider-ish network, and witnesses see session metadata. Not maximal decentralization, just less centralization.
- The version you actually want — a permissionless attester committee: anyone can join the MPC leg, no single operator to trust, slashing for lying. That's not a shipped product anywhere afaik. Quilibrium's Compute/MPC direction points at exactly this kind of thing, but I don't have docs saying zkTLS is live there — check docs.quilibrium.com before commissioning anything.
On "I don't want to run a server/node": if the attester is a decentralized network, you don't run one — you dial in as a client. The network runs it. That's the entire pitch of using a decentralized substrate instead of a hosted notary.
But separate your goals: if you want privacy of traffic, zkTLS is the wrong tool — onion-routed encrypted transport gets you there with no attesters at all. zkTLS only earns its keep when you need a proof for someone else. Which one are you actually after?
-# I can make mistakes · always check official docs · if I'm wrong, tell me the right answer and I'll flag it for review
What the user corrected:
In a zkTLS/HTTPS-proof discussion the bot recommended "Garnet (fairgate)" as a no-notary option from training memory; user could not find it and the bot had to retract. Maintainers should add verifiable, current documentation on zkTLS approaches (DECO, tlsn/TLSNotary, Reclaim, threshold-notary MPC like Opacity) with source links and SDK/readiness status, and ensure the bot only names projects it can anchor to a source. User also noted Opacity lacks an active web SDK — worth tracking that in the doc.
Original question:
no what i'm saying is i want to generate https proofs. i can use an intermediary only if it is maximally decentralized. see opacity network for example. i do not want to run a server/node myself to eliminate the third party.
This issue was automatically created by Quily from a Discord correction.
Correction (via Discord)
Reported by: Mahatma Gandhi
What Quily said:
What the user corrected:
Original question:
View original message on Discord
This issue was automatically created by Quily from a Discord correction.