Alex

@madhavanmalolan @reclaimprotocol @ericmigi @Pebble 🥲

Finally got our annual merch into hands of the @reclaimprotocol team! This is easily the best merch ever for us! Huge thanks to @ericmigi & @Pebble for making this happen. It wasn't easy shipping this to a global team - but they made it happen without a fuss!

TEEs shifted trust from @reclaimprotocol to @AMD. That's an easier trust assumption to make for an enterprise.

We were able to earn trust by showing all our code is verifiable via cryptography. Enterprises understand TEEs. It was a pleasant surprise. Many of them already run sensitive workloads on TEEs in Google Cloud/Azure/AWS.

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.

1/ Part 2: What buyers should be asking their verification vendors. The best verification systems don't rely on a single method. They use a waterfall. Try the most private method first. Fall back only when needed. Here's what that looks like:

1/ The verification market is being rewritten. Most vendors are solving it wrong. @Reddit : £14.47M fine. @Meta : facing up to 6% of global revenue. @Pornhub : blocked in 23 states + UK + France. @getyoti : €950K fine for biometric handling. The fines aren't the story. The WHY is (Thread)

Guarantee #2 : We ensure that data you get is tamper proof. Enabling businesses to take decisions quickly and confidently looking at user data.

We were audited by @zksecurityXYZ , @zellic_io, @CommonPrefix ; That's the truest form of an audit today, even with advanced AI models. At the same time, we cannot afford to have a 3 year gap between audits this time around - when we're pushing new code every hour.

We acknowledge there will always be new surface areas of attack. So, we have to be proactively look for those potential attacks ourselves.

Introducing Reclaim Protocol Trust Center. Visit : trust.reclaimprotocol.org

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.

@Bobchensk Это два предложения, долбоёб

И это первый раз, когда слова "хор монастыря" и "хэдлайнер" встретились в одном предложении

Very excited to be organizing an event focused on building defensive solutions for the deepfake onslaught, during @a16z @Techweek_ in NYC this summer! The only effecive way to fight AI generated fraud is using cryptography, not "better AI". Registration links below 👇

Two announcements this week: the #EU launched its #ageVerification app, and @worldnetwork launched proof-of-humanity integrations with @Tinder , @Zoom , and @Docusign . One requires you to scan your passport. The other requires you to scan your iris. Both assume you need new hardware or documents to prove something the internet already knows about you.

#EU #AgeVerification app was launched yesterday. Enrollment was limited to passport NFC scan/eIDAS node. So, built an enrollment connector that lets users prove age_over_18 from their bank, government portal, or any web source that holds their DOB via @reclaimprotocol. Plugs directly into the EU issuer. Same mdoc attestation out the other end.

Someone on the FFmpeg mailing list claims to have built a superoptimiser that beats hand written assembly. We'll find out soon enough

Ok I'm done with @claudeai for the day 😆

Meet TeleGO - (very) fast MTProxy implementation with TLS splicing github.com/Scratch-net/te… #telegram #sensorship

Built @reclaimprotocol MCP server today. Devs using @claudeai code can integrate Reclaim verification into any project with 2 commands and a single prompt. Auto detects your stack, installs the SDK and writes all the verification code automatically. - npm install -g @reclaimprotocol/mcp - claude mcp add reclaim -s user -- reclaim-mcp Just tell @claudeai Code to integrate Reclaim with your App ID, Secret and Provider ID from dev.reclaimprotocol.org . [Demo Attached]

an update on zktls from someone who's running sales and GTM for @reclaimprotocol the term 'zktls' was extremely popular back in q2 2025 and for good reason - a lot of the user data that was locked behind walls were now accessible. 1/ social data: detailed user data like demographics, unique views, analytics and insights were now easily fetched from platforms like tiktok, instagram, youtube, X without scraping (illegal) or using their APIs 2/ financial data: your bank balances, transactions, proof of payments are now accessible without relying on account aggregators. 3/ university/ employment credentials: proving that a student is indeed enrolled in X university is extremely easy without having to go about (1) uploading documents (2) direct integrations with unis/ portals. last year the only bottleneck was that you needed to either (1) download an app (eg: @OpacityNetwork) or (2) download an extension (eg: @primus_labs). this was a huge UX issue for web2. multiple companies turned us down because this was the case. we knew that without solving this we could never break the bubble. so after months of r&d we’re excited to announce that we’ve finally built a production ready flow where the user can verify their user data without (1) downloading an external app/extension (2) being redirected someplace else and with a completely customisable UI (zero mention of a third party service) kudos to @madhavanmalolan @HarshaKaramchat @abdul_rashid_r and the whole engineering team