Reclaim protocol uses https session keys to generate zk proofs of user's profiles, enabling verifiable credentials without APIs.
Last 6 months · Weekly commits
The attestor-core (aka witness server) securely intermediates internet data exchange, using TLS and zero-kno…
JavaScript SDK for easy integration of Reclaim Protocol that enables authenticated web data export via HTTPS…
Automated discovery of universities’ student login portals.
Browsers-as-a-service for automations and web agents
TEE implementation
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.
TEEs are a superpower for startups to punch above their weight. Many startups aren't able to close deals because large enterprises don't trust said startup. But they all trust AMD, Intel, Google, Microsoft, Amazon already. TEEs let you ride on that.
You can't trust TEEs blindly. They do get compromised from time to time. But the question is, how can you minimize the surface area? Multiple TEEs across multiple vendors.
Great discussion - Implementing a novel architecture SplitAEAD - What TEEs are useful for - Developer challenges setting up TEEs between @madhavanmalolan and @NoiseSocket
You can watch the full episode here with me and @NoiseSocket : https://www.youtube.com/watch?v=nHNAAlQ-q70
v3 of Reclaim Protocol has landed. SplitAEAD over TEEs.
We've been working on a new architecture for Reclaim Protocol for a while. We call it SplitAEAD. A complete rewrite with improved performance, privacy, and trust assumptions. We split AEAD into…
