[vvpan]

A cool technology that builds on ZK is zkTLS that can prove that you have access to some data on the internet, for example that you have an account with some service without revealing your username. So more private oauth I suppose?

[baby]

Great intro to how zkTLS works: https://blog.zksecurity.xyz/posts/zktls/

[EulerLagrange]

im in the background of that talk

[vvpan]

Lagrangodamus!

[dungeonsndregoo]

A technical deep dive into how zkTLS works with MPC architecture: https://paragraph.com/@vinny/opacity-network-deepdive

[Sancty]

I'm excited for this to be mainstream. OAuth is definitely a step in the right direction, but many times scopes are broader than they need to be and can be abused. AFIAK, zkTLS can provide derivate values; i.e "You are over 18" (T/F?) verse "Your birthdate is".

[skaramchati]

Reclaim Protocol, a YC company, is building an open sourced version for zkTLS. This has been by far the most widely adopted zkTLS project.

You can read the docs and whitepaper here: https://docs.reclaimprotocol.org/ And also take a look at all usecases built on top of this tech: https://reclaimprotocol.org/ecosystem

[dop42069]

It works for private user data in adversarial setting. Like the outcome of a rocket league match can settle a $20 bet. Showdown.win

[tucnak]

This is perhaps more important in the age of AI agents, but before we can tackle all these fancy ZKP constructs in the mainstream — we have to, as the industry (and so far consistently failed to) — implement Zanzibar, or whatever ReBAC, and maybe ZKP stuff could "sneak in" that way, in the form of zero-knowledge warrants, or whatnot. Unfortunately, even though it works consumption-wise, it's fundamentally at odds on the provider side.

The providers are clutching their OLAP like pearls! :-)

[TuretzkyRon]

but the server side does not have to support it on their end for it to be used