zkTLS has two ways of establishing trust in web data, and the difference comes down to how the TLS connection is handled. @primus_labs supports MPC-TLS and Proxy-TLS. → MPC-TLS uses secure multi-party computation during the TLS handshake. the client and attestor work together, preventing the client from independently altering the data before the attestor provides its key share. Primus uses QuickSilver to reduce the overhead. → Proxy-TLS the attestor forwards TLS traffic and records encrypted messages. the client then proves knowledge of the underlying plaintext. this avoids the MPC interaction and offers better performance, but introduces an additional trust assumption around the attestor’s connection to the intended server. → the trade-off MPC-TLS prioritises protection against client-side tampering, while Proxy-TLS reduces overhead for better performance. the right choice depends on the application’s security and performance requirements. check it out here: https://t.co/Fm2Bkqwkwi