Reclaim Protocol
3.5K posts
@reclaimprotocol
Verify any data on the internet in seconds with zkTLS!
Implementing SplitAEAD @reclaimprotocol meant tweaking the TLS stack itself, without breaking security or compatibility.
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.
You can watch the full episode here with me and @NoiseSocket : youtube.com/watch?v=nHNAAl…
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 two independent steps, that's executed by independent TEEs.
It is incredibly important that Reclaim Protocol proofs are tamper resistant. It should not be possible for a malicious user to be able to fake a verification. That's the guarantee we strive for, that's the reason we exist.
On Reclaim Protocol Trust Center, we set up a trip-wire for ourselves. We sample random sessions and look for any stored or transmitted PII. Ideally, NO PII should ever leave the client.
Very excited to launch Reclaim Protocol's Trust Center. A transparent way for us to showcase the commitments we make, and how we keep (or not keep) said commitments.
