Reclaim protocol uses https session keys to generate zk proofs of user's profiles, enabling verifiable credentials without APIs.
Last 6 months · Weekly commits
Reclaim Protocol's InApp React Native SDK for ZK proof generations for requests with an in-app experience of…
Self-hostable browser runtime infrastructure for agents.
Reclaim Protocol's InApp Flutter SDK for ZK proof generations for requests with an in-app experience of web …
Reclaim Try Website
TEE implementation
Reclaim Protocol's InApp Capacitor SDK for ZK proof generations for requests with an in-app experience of we…
Open sourcing our Remote Browser in a TEE over x402!
Meet Popcorn, the browser cloud we built at @reclaimprotocol It runs browsers inside TEEs: secure by design, fast to start, and usable by both people and agents. Here’s how and why we built…
Please note. How you get help from the Reclaim Protocol team just changed. The new touch point is [email protected] Good old email.
If you are using @reclaimprotocol and need help, please note that the telegram community group is deprecated. We are still actively helping though! Shoot us an email - [email protected]
Do check out this 3min interactive explanation to understand how Reclaim Protocol :)
We put out an interactive explanation of how Reclaim Protocol works. Check it out, link below.
Devil is in the detail for a secure implementation of a protocol.
Implementing SplitAEAD @reclaimprotocol meant tweaking the TLS stack itself, without breaking security or compatibility.
