-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PoC: Migrate to Prosopo #337
Comments
Thanks for writing this up @Bullrich! We'll start on an implementation early next week. |
Hi @Bullrich do you have element so we can chat about the PR? Thanks |
It would be interesting to have the ability to configure either standard recaptcha provided by Google or Prosopo. As long as we don't remove existing "production" captcha solution. I'm all for migrating to decentralized captcha, especially if it is built on Polkadot ! |
Hi @PierreBesson, no problem. We'll add a feature flag in to enable Google or Prosopo. |
I'm thinking this is excessive. Procaptcha either will work and we will use it, or it won't prove itself reliable and we'll revert the changes. Supporting two systems at the same time doesn't have a practical application IMO. |
Me and @rzadp have been in touch wit the guys from Prosopo and they have a decentralized captcha system currently on the Rococo parachain: prosopo/captcha.
It would be interested to create a Proof of Concept to see how it works and to consider replacing google captcha for this alternative.
The implementation of Google captcha in the client can be found in: CaptchaV2.svelte
For the server we have this class: Recaptcha.ts
The text was updated successfully, but these errors were encountered: