---
# System prepended metadata

title: 'Navigators Season 2: Growth Grants Proposal of Reclaim Protocol'

---

# Navigators Season 2: Growth Grants Proposal

## Title
Reclaim Protocol Integration with Mina

## Project Background
Reclaim Protocol makes https traffic verifiable using Zero-Knowledge Proofs, enabling users to generate verifiable credentials from any of their online user profiles. This unlocks unlimited possibilities as no APIs are required to extract the data or no changes to be made to the websites, while guaranteeing data integrity. Web2 user data which was elusive to Web3 till now will be available across dapps on Mina. 

This opens up opportunities for a new wave of applications in privacy, sybil resistance, proof of personhood, KYC and many more. Dapp developers can leverage Reclaim protocol to build multiple use cases related to KYC, sybil resistance, proof of personhood, etc on top of Mina using Reclaim protocol.

Visit this [blog](https://www.reclaimprotocol.org/blog/posts/what-is-reclaim-protocol) to learn more.

## Proposal Overview
Reclaim Protocol seeks to integrate with the Mina ecosystem to address the challenge of securely and privately using Web2 data in Web3 applications. By leveraging zero-knowledge proofs (ZKPs), Reclaim enables users to generate verifiable credentials from their Web2 profiles (e.g., Twitter, GitHub) without requiring centralized APIs or platform changes. 

- **Problem:** Web3 applications lack access to **verifiable Web2 data**, making it challenging to integrate online user profiles, activity metrics, and credentials into decentralized ecosystems. This limitation hampers innovation in areas such as KYC, proof of personhood, identity verification, and dApps requiring trusted off-chain data. Current solutions often rely on centralized APIs, which are fragile, expensive, and lack scalability. Moreover, these approaches do not guarantee cryptographic verifiability or preserve user privacy, further restricting broader adoption.



- **Solution:** Reclaim Protocol bridges the gap between Web2 and Web3 by allowing users to generate cryptographically verifiable credentials from any online profile using Zero-Knowledge Proofs (ZKPs). It makes HTTPS traffic verifiable, enabling users to share specific data (e.g., Twitter followers, GitHub contributions, or account activity) without exposing sensitive details. The solution is requires no changes to Web2 platforms, and provides secure data portability with user consent.

- **Impact:** 
Reclaim Protocol's integration with the Mina ecosystem will:
  - **Encourage Adoption:** Enable dApps to leverage Web2 data, attracting developers and users who can build novel applications on Mina.
  - **Foster Innovation:** Unlock use cases like verifiable identity, Proof of personhood, Sybil resistance, and proof-of-reputation-based systems and many others.
  - **Expand Mina’s Reach:** Provide tools for developers to tap into real-world data, increasing utility and encouraging ecosystem growth.
  - **Promote Privacy-Preserving Solutions:** Showcase Mina’s lightweight zk-SNARK architecture alongside Reclaim’s ZKP-based verifiability, positioning Mina as a go-to platform for privacy-focused apps.
- **Audience:** The target audience includes developers and teams looking to leverage zkTLS infrastructure to build novel applications requiring verifiable data from the Web2 world. This spans decentralized application developers creating solutions for identity verification, KYC, sybil resistance, proof of personhood, and credential verification.



## Architecture & Design


- **Detailed Design/Architecture:**
Reclaim empowers users to generate Zero-Knowledge Proofs for any online user profile. To generate a claim, users first need to log into the relevant website. This login process, involving an HTTPS request and its subsequent response, is channeled through an HTTPS Proxy Server known as an 'attestor'. This attestor oversees the encrypted data exchange between the user and the website. Subsequently, users provide keys that disclose non-sensitive parts of the request to the attestor. With this, the attestor can view the request in its entirety, barring confidential details like authentication data, and can confirm its legitimacy.

  The website's encrypted response is then processed by a zk-circuit, which identifies a regex match within the encrypted data using a decryption key as a confidential input. The attestor further validates that the zk-circuit's public input was indeed the encrypted data sourced from the website. With these attestations on both the request and the encrypted response, coupled with the zk-proof, any third-party application, whether on-chain or off-chain, can verify the existence of data that exists on the user’s profile.
  
  ![Untitled](https://hackmd.io/_uploads/rkl483BQ1g.png)

  ![Untitled (1)](https://hackmd.io/_uploads/ByCH83SQkg.png)
User credentials in Reclaim Protocol are generated and stored completely on the client side. Using Reclaim, users can generate Proofs(Groth16) in less than 4 secs even on a 2015 Android Device! 


- **Vision:** Reclaim aims to supercharge Mina Ecosystem by enabling both access to users' onchain and offchain credentials. 

    1. **Enhanced Interoperability**: 
    - By allowing Dapps on Mina to access data from Web2 platforms, we can significantly expand the range of applications and use cases that can be developed on Mina, especially those focussed around KYC, sybil resistance, proof of personhood, thus driving significant ecosystem growth.
    2. **User-Centric Data Access:**
    - Reclaim’s commitment to self-sovereignty and user consent in data access aligns with the decentralized and user-centric principles of the Mina ecosystem. This ensures that Dapps built on Mina utilizing Reclaim Protocol are adhering to robust data privacy and user consent norms.
    3. **Enabling New Use-Cases:**
    - By facilitating access to off-chain user data, Reclaim Protocol can enable the development of [new, innovative use-cases](https://www.reclaimprotocol.org/blog/posts/usecases-to-build-reclaim) on Mina, such as Skill IDs, P2P onramp/offramp, Gossip marketplaces, or social Dapps that utilize user data from Web2 platforms.
    4. **Enhanced Developer Mindshare:** 
    - By facilitating new and unique use cases that leverage off-chain data, Reclaim protocol will attract a broader developer community to Mina, enriching its ecosystem and increasing its competitive edge
    
- **Existing Work :** [Github](https://github.com/reclaimprotocol)
- **Production Timeline :** Our product is production-ready, and we estimate the integration with Mina will be completed within 3 months.



##  Budget & milestones

- **Deliverables**:
  - **Reclaim Integration:** 
    - Research o1js and Mina core protocol, its design, and architecture and share implementation specification documents with the o1js team for feedback and comments
    - Reclaim’s integration with o1js as zkOracle
  - **Documentation & Testing:** Comprehensive documentation, blogposts, and participation in Mina’s developer community 
  - **Ecosystem Integration & Community Engagement:** Launch of 2 Dapps on production within the Mina ecosystem that integrate Reclaim protocol or build at least 2 usecase unlocked uniquely because of Reclaim protocol
- **Mid-Point milestones:** Integrate foundational zkTLS infrastructure and conduct internal testing.
- **Project Timeline :** 3 Months
- **Budget Requested :** 56,000 MINA
- **Budget Breakdown:** 
  - Reclaim Mina Integration - 37,500 MINA
  - Comprehensive documentation, blogposts, and participation in Mina developer community - 6,000 MINA
  - Integrate with 2 dAppps from Mina ecosystem- 12,500 MINA
- **Wallet Address:** B62qoApnTMRBZDLqt8KrVX7eh4hA5wxrtGoxqdiiF7QkH71yimNAT1y



## Team Info
Reclaim Protocol is built by the team at CreatorOS Inc. We are a 35+ member engineering and web3 product development & research team including ZKP researchers and with previous affiliations to Stanford, Microsoft, Meta and Google . We have also built - [Questbook.app](http://Questbook.app), an industry leading on-chain grants management tool that is used by some of the major L1/L2s including Polygon, Solana, Compound, Arbitrum , TON, among others.  CreatorOS is a YC W21 company.

- Madhavan Malolan : CEO
    - Building in crypto since 2016.
    - Among first 5 contributors to Plasma (ethereum scaling solution) specifications.
    - Open source contributor.
    - ex-Microsoft, Computer Science IIIT-H.
    - [LinkedIn.](https://www.linkedin.com/in/madhavanmalolan/) [Github](https://github.com/madhavanmalolan)

- [Kirill Kutsenok](https://www.linkedin.com/in/kirill-kutsenok/), Cryptography & Security Researcher
- [Adhiraj](https://www.linkedin.com/in/adiwajshing/) Singh: Lead Developer
- Aleksai Ermishkin: Lead Blockchain Developer


## Risks & Mitigations

**Risks:**
**Centralization:**
There are 3 nodes on the network, hosted on an AVS Holesky testnet. All three nodes are currently run by us (CreatorOS Inc). 

Though we do intend to decentralize it, at the time of this writing - we are very much centralized.

**Technical Dependencies:**
Reliance on zkTLS and its cryptographic systems means unforeseen vulnerabilities or bugs could impact development timelines or security.

**Mitigations:**
**Transition to Decentralization:**
A phased approach is planned to onboard more independent validators into the network, increasing trust. This will also distribute the workload across multiple nodes for better resilience.

**Robust Testing:**
Conduct rigorous internal and external security audits for zkTLS to identify and patch vulnerabilities early. Regular stress tests will ensure system stability under load.