Reclaim lets your users prove and import identities and reputations they have on other websites. From bank balance in the bank account to Uber rides they’ve taken, while maintaining data security and privacy.
Hey everyone! Co-founder of Reclaim here. 👋
We have been building Reclaim Protocol for the last 2 years. Reclaim Protocol, at its fundamental, is a cryptographic breakthrough. I am happy to talk about the specifics, but in the interest of brevity, I’d say Reclaim Protocol makes HTTPS verifiable. HTTPS, which powers all our websites, is by definition private. But it is not verifiable. That is, if you saw certain contents on a webpage — there is no way for you to prove to me that indeed was what you saw.
The only way you probably have right now to tell me what showed up on your browser is to take a screenshot and send it to me. That usually works in peer-to-peer settings. However, a screenshot is too easy to morph for it to have any business usecases.
That changes with Reclaim Protocol.
Because Reclaim Protocol makes HTTPS verifiable, you can open a page and generate a cryptographic proof of what was displayed on your screen. Even better, you can hide sensitive data without compromising the integrity of the cryptographic proof.
I am very excited to present to you an early version of the Reclaim Protocol SDK. I am sure we’ll have another launch on Product Hunt with a more advanced feature set. But today’s launch is for the tech-curious developers. The developers who want to explore the bleeding edge of technology. The developers who move the entire industry forward. The developers who are our mavericks, our heroes.
This SDK lets you request and accept cryptographic proofs of what the user saw on their browser when they opened a webpage. This is particularly useful for applications where you want to see what showed up on websites that are behind a username password. So instead of accepting screenshots and having to verify the authenticity of the screenshot, you can just accept a cryptographic proof that gets created and verified in seconds.
We have put in a lot of work, and continue to put a lot of work to make it super duper easy for you to integrate. We have a developer portal where you can get started with an integration in under 10 minutes — we give you copy-pastable code that just works out of the box! Because that’s the kind of devX I want for myself when I’m integrating other SDKs.
We support over 100 websites from which you can import users’ profiles, reputations, and other data. If the website you care about is not on the list, you can build an integration yourself using the same developer tool. Now that part is evolving super fast and I personally would be more than happy to extend a helping hand to build this integration.
We also wrote about some of the usecases that we are excited about that can be built using Reclaim Protocol, but couldn’t be built before here: https://blog.reclaimprotocol.org...
I cannot wait for you to try out our SDKs, and cannot wait to see what you build!
It sounds like a revolutionary solution for making HTTPS verifiable, addressing a crucial need in web security.
Quick question: How does Reclaim Protocol safeguard against potential vulnerabilities or attacks on the cryptographic proofs generated? Congratulations on the launch tho! 🎉
I recently had the chance to evaluate the mechanics of the Reclaim Protocol SDK, and I must say that I was thoroughly impressed with its ingenuity. The potential for utility and application of the SDK seems limitless, and it has the ability to bridge the gap between web2 and web3 in a simple and user-friendly way. This is definitely a move in the right direction towards merging web2 and web3. I can't wait to see which products this will integrate with!
Reclaim Protocol SDK (Alpha)