Had someone on twitter think they know more than me about zkTLS.

Test your understanding and see if you can spot why this person is wrong without opening the thread.

cc @avichalp

@lithdew @AFDudley0 @hdevalence @OpacityNetwork All i said was its 30s default on nginx.

&gt; point me to the specific part of the protocol that makes it necessary to generate the proof during the request.

We use mpc. You have to:

1. Open socket connection
2. TLS handshake in mpc
3. Encrypt request (potentially in mpc)
4.… https://t.co/LCLAOGi1kd

@Euler__Lagrange @AFDudley0 @hdevalence @OpacityNetwork It takes a few seconds to generate a ZK proof to prove a merkled TLS trace (MPC isn’t necessary but also takes only a few seconds either way). How you got to having to deal with timeouts is what I’m not understanding here and what I’d like you to point out.

Kenta Iwasaki

Had someone on twitter think they know more than me about zkTLS.

Test your understanding and see if you can spot why this person is wrong without opening the thread.

cc @avichalp 

https://x.com/lithdew/status/1875026558899089900?s=46

Working on building zkTLS infra/products. A ruthless empiricist and meme connoisseur.

/opacity
/eulerlagrange

also, i don’t think he is acknowledging the fact that if a server can easily distinguish between a normal TLS connection versus an MPC TLS connection it will just block you