Comment by davidmurdoch

3 years ago

I'm at a loss for how this could be implemented reliably (where it never fails to stop bots). Ideas?

I don't think the burden of proof/R&D is on us. But there are many smart people around, I'm sure Cloudflare can pay some of them (even more surprising things are possible with cryptography).

One far-fetched idea is to use ZKP proofs to prove that you were verified, without disclosing anything your identity. But that's likely overkill.

Anyway, I think Cloudflare already works on something better with turnstile, the "privacy preserving captcha" and private access tokens [0].

[0] https://blog.cloudflare.com/turnstile-private-captcha-altern...

What do you see as the problem with this attempt?

https://privacypass.github.io/

  • It allows for unlimited tries. Let's say current ML system could solve 1% of the captchas, then an attacker could try a million captchas and generate privacy passes for equivalent of 10k captchas.

    Theoretically, to penalize the user you need to identify the user. And for that you need to maintain long term identity.

    • You still wouldn't need that.

      Trivial counter-examples include proof-of-work (see HashCash) or cryptocurrency micropayments (not necessarily settled on-chain, so transaction fees are not an issue for the user).