Reclaim Protocol

Every blockchain application faces the same cold-start problem: on-chain history tells you almost nothing about who a user is. A wallet could belong to a physician earning $300,000 a year or to a bot farm cycling dust transactions. Without access to the web2 world where identity, income, education, and reputation actually live, decentralized finance and other on-chain applications must either over-collateralize to absurdity or simply refuse to serve users who have not built extensive on-chain histories. Reclaim Protocol is infrastructure designed to close that gap.

The protocol enables users to generate cryptographic proofs of data that exists behind any login wall — bank balances, employment records, university enrollment, purchase histories, social media follower counts — and export those proofs to any application that wants to verify them. The user never hands over their credentials. The receiving application never sees the raw data unless the user explicitly discloses it. What passes between parties is a verifiable attestation, not a data transfer.

The underlying technology is called zkTLS, a combination of two well-established primitives. TLS (Transport Layer Security) is the encryption protocol that secures almost all web traffic. Zero-knowledge proofs are cryptographic constructs that let a prover demonstrate knowledge of a fact without revealing the fact itself. Reclaim Protocol wires these together through a proxy-based architecture: when a user navigates to a source website, their traffic routes through an attestor node that observes the encrypted exchange. The user shares a fractional portion of the session key with the attestor, which is enough for the attestor to confirm the server authentic response without being able to read the full contents. A zero-knowledge circuit then runs client-side to extract only the relevant data slice — proving, for instance, that a bank balance exceeds a threshold without exposing the actual figure or any other account details.

The ZK component serves two distinct purposes. First, it protects the decryption key from the attestor, preventing any third party from using a captured key to read historical communications. Second, it enables selective disclosure — the user proves they are enrolled at a university or employed by a specific company, not that they have a 3.8 GPA or earn a specific salary, unless they choose to reveal more. The attestor produces a portable signature once verification is complete. That signature travels with the user and can be presented to any application configured to accept it, without requiring any further contact with the source website.

Developers access the protocol through a self-serve SDK and API. The integration model supports three patterns: a fully pre-configured flow for major institutions such as universities and large payroll providers, an agent-assisted setup where AI tooling helps define how to extract data from any site, and a manual SDK path for custom implementations. The team has also released zkFetch, an extension of the same mechanism that works on public API responses rather than authenticated sessions, enabling verifiable data retrieval even without a user login.

Provider creation — the process of teaching the system how to extract specific fields from a specific website — was historically a bottleneck that required Reclaim's team to build each connector manually. The team released a developer tooling layer that lets anyone define a new provider by specifying a URL and the data path (JSON or Xpath) where the target field appears. The community has built over 200 providers using this tooling without Reclaim's involvement. The team later added AI assistance that accelerates provider creation further, automatically repairs providers when a website changes its HTML structure, and can generate providers dynamically for sites where no pre-existing provider exists.

The platform has processed over four million verifications across education, employment, income, loyalty, and identity categories. Coverage spans 29,000-plus universities and major enterprise payroll systems including ADP, Workday, Paychex, and Gusto, as well as government tax portals and gig economy platforms. Pricing is self-serve and transparent: a free tier covers 25 verifications per month, scaling to $0.10 per verification at enterprise volume. The platform holds SOC 2 Type II and ISO 27001 certifications and is GDPR-ready, with cryptography that is open-source and independently audited.

Reclaim Protocol is multi-chain by design. The team has deployed on Solana, enabling developers in the Solana ecosystem to pull verifiable web2 data into their on-chain applications. The protocol is also active on TRON, Cardano, and NEAR. On Solana, the live integration means that lending protocols, airdrop campaigns, DeFi applications, and identity layers can gate access or set terms based on verified off-chain credentials — income for undercollateralized loans, social proof for reputation systems, national identification for compliance checks.

Use cases that have emerged across the ecosystem include undercollateralized DeFi lending where income verification replaces or supplements overcollateralization, token airdrop qualification tied to verifiable web2 activity rather than just on-chain history, proof-of-personhood layers for applications that need to exclude bots, secondary KYC flows that verify identity without collecting raw documents, and cross-platform loyalty programs where a user status on one platform is recognized by another. A student verification integration has demonstrated a documented lift from seven percent to forty-four percent conversion on enrollment-gated platforms. Recent blog posts through April 2026 describe emerging use cases including age verification for regulatory compliance and crowdsourced national digital identity systems.

The broader significance of zkTLS as a technology class is the subject of active academic attention. Reclaim Protocol work has been cited in peer-reviewed research including papers presented at AFT 2025 and ACM 2026, and the protocol participated in the zkTLS Day track at Devconnect 2025 alongside other implementations such as TLSNotary. The competitive landscape includes DECO from Chainlink, zkPass, zkMe, and Opacity Network — each with different trust models (MPC, TEE, or proxy-based) and different tradeoffs between computational cost, hardware dependencies, and decentralization. Reclaim operates primarily in the proxy model and uses ZK proofs to minimize the trust placed in the attestor.

For Solana developers, Reclaim Protocol represents a practical on-ramp for applications that have outgrown what on-chain data alone can support. The protocol is live, documented, and developer-accessible through a self-serve API portal at reclaimprotocol.org.