Reclaim Protocol

Reclaim Protocol is a zkTLS infrastructure layer that lets users generate tamper-proof cryptographic attestations of data from any authenticated website, bringing Web2 identity, reputation, and activity data verifiably on-chain.

The problem

Web3 applications have no reliable way to access who their users are outside the blockchain. A DeFi protocol cannot know a user's credit history; a DAO cannot verify a member's professional credentials; a lending platform cannot confirm employment without asking users to hand over document copies that can now be trivially forged by AI. Legacy verification services address parts of this problem but are expensive, slow, and limited in geographic or data coverage.

At the same time, users accumulate rich reputational and transactional histories across Web2 — ride counts on Uber, degrees verified through university portals, income through payroll systems — but have no portable, cryptographically verifiable way to share that data with applications without exposing credentials or trusting a centralized intermediary to vouch for them.

How Reclaim Protocol works

The core technology is zkTLS (Zero-Knowledge Transport Layer Security), which integrates zero-knowledge proofs into standard HTTPS connections. Rather than scraping or re-hosting data, Reclaim lets users prove specific facts about data they can already see on authenticated websites, without revealing their passwords or any surrounding private information.

Technically, it uses a proxy-based attestation model. When a user authenticates with a target website — a university portal, a payroll system, a social platform — their HTTPS traffic is routed through a Reclaim attestor node. The attestor observes encrypted packets but not the plaintext. The user shares partial decryption keys with the attestor, which verifies the TLS handshake occurred with the correct domain and then produces a cryptographic signature. Zero-knowledge circuits run client-side to search the decrypted response and extract the target claim. The resulting attestation is a compact, shareable proof that a specific data point appeared in a real server response — without exposing anything else from that session.

A "provider" — Reclaim's abstraction for a data source — consists of two elements: a URL pointing to the page containing the data, and a JSON path or XPath identifying exactly where the relevant value sits within the response. The protocol ships with pre-built providers for thousands of websites; developers can build custom ones using open-source SDKs or by prompting an AI agent.

AI-accelerated provider building

A persistent challenge with this class of infrastructure is maintenance: websites redesign layouts and break existing selectors. Reclaim has integrated Claude (Sonnet model) to navigate pages visually, identify data across multiple sub-pages, and auto-repair broken providers when upstream sites update. This reduces downtime from hours to minutes. It also allows developers who lack an account on a target website to specify the data they want — the AI-assisted flow completes provider construction when a real user authenticates.

Products and use cases

The most mature commercial offering is credential verification — employment and education — targeting HR, fintech, and compliance workflows where document-based verification is increasingly unreliable in an era of AI-generated fakes.

Key products include:

• Employment and income verification: Covers 90+ countries via payroll systems, tax portals, and gig platforms. Returns verified employer, title, and gross income.
• Education enrollment verification: Covers 29,000+ institutions across 190+ countries through direct university portal connections, replacing uploaded transcripts with source-based verification.
• zkFetch: Verifiable API calls that prove the contents of a server response without requiring end-user authentication — useful for integrating open APIs into trust-minimized pipelines.

Beyond credentialing, the SDK enables a wide range of Web3 use cases: proof of personhood, social reputation import (follower counts, engagement histories), KYC augmentation, credit scoring from on-chain and off-chain histories, and import of user preferences or purchase history for targeted DeFi products. The team argues that source-based verification eliminates the attack surface that AI-generated document fraud exploits, since the data originates directly from the institution's own authenticated portal.

On-chain integration and Solana

Reclaim Protocol deploys smart contracts on 15+ blockchains, allowing any on-chain application to verify a Reclaim proof natively. Supported chains include Solana, all major EVM networks, Aptos, Sui, NEAR, Starknet, Cosmos, Polkadot, and Stellar. A dedicated Solana SDK and example repository allow developers to submit and verify proofs via Solana programs, making Reclaim attestations composable with any Solana application.

SDKs are available for web (JavaScript/TypeScript), mobile (Flutter, React Native, Kotlin, Swift), and on-chain environments across all supported chains.

Security model and academic recognition

The proxy attestor approach is computationally efficient — proof generation takes 2 to 30 seconds — but requires trust in the attestor not to collude with users to fabricate data. Reclaim mitigates this with a network of attestors rather than a single centralized witness. This contrasts with MPC-based zkTLS systems like DECO, which distribute trust across multiple parties but require substantially more computation. Reclaim's whitepaper has been cited in peer-reviewed academic work including papers presented at AFT 2025, USENIX 2024, and ACM 2026.

Traction

The platform has processed over 4 million verifications. Public pricing tiers range from a free developer tier (25 verifications/month) to enterprise contracts starting at 0.10 USD per verification, with one reported customer improving education verification conversion from 7% to 44%.

Ecosystem fit

Reclaim Protocol addresses one of the persistent gaps in the Solana ecosystem: the lack of a trust-minimized bridge between authenticated Web2 data and on-chain state. Protocols wanting to gate access based on real-world credentials, build credit products, or tie off-chain reputation to on-chain identity without centralized oracles have few alternatives at comparable cost and coverage. Native Solana smart contract support positions Reclaim as composable infrastructure for the on-chain identity, reputation, and compliance stack.