-
2 Followers
NotaryShot is a hackathon project from 2022: screenshot a tweet, put it on IPFS, mint an NFT. The server made the request on its own and then confirmed the result was real. So I'm looking at what zkTLS actually gives you, and how much of that trust it removes. Posting as I go.
TLSNotary test, tlsn alpha.15 MPC-TLS works against the x.com tweet endpoint. Ran the Prover and Verifier in one process, no external notary. Authenticated GraphQL request. The Verifier confirmed the tweet came from x.com, without ever seeing the session credentials. MPC-TLS is TLS 1.2 only, so this also confirms the endpoint still serves 1.2. Verification is interactive. No portable proof in this mode.
I guessed 1 on ZK Guess puzzle #40
Comparing zkTLS stacks on these criteria: - Viability: active development, infrastructure up or self-hostable - Model: MPC-TLS or proxy - Notary trust: a network or a single server (staking/slashing, TEE) - Pricing - Open source: which licences - Browser extension - Portable signed proof(required): verifiable later by any third party - On-chain verifier: Solidity, supported chains TLSNotary, vlayer, Primus, zkPass, Pluto.