{"signature": "0x96bce4346d1f1b8beb6241478a3e662713ba10d3e325fd8bea95ffc63edf82a3047f46f93c16c4bdd4eb17620959b24981be8cb2abd7dc3864fcf7540f7ef5071c", "application": {"round": "0xe5B88c67fCd25f0a7BAD6cF7c5A5197e61BFd143", "answers": [{"type": "email", "answer": "kaz@cubid.me", "hidden": true, "question": "Email Address", "questionId": 0}, {"type": "short-answer", "answer": "kazanderdad", "hidden": true, "question": "Telegram Handle We Can Use To Contact You", "questionId": 1}, {"type": "paragraph", "answer": "cubid-me", "hidden": false, "question": "Project GitHub Repo", "questionId": 2}, {"type": "link", "hidden": false, "question": "Link to your Public Group Chat", "questionId": 3}, {"type": "paragraph", "answer": "No", "hidden": false, "question": "Have you participated in a previous Gitcoin Grants Round? If so, please name the rounds or link the builder profile associated with previous rounds", "questionId": 4}, {"type": "paragraph", "answer": "**Cubid SDK** is an open-source toolkit that helps developers seamlessly integrate **decentralized identity**, **reputation data**, and **non-custodial embedded wallets** into their Web3 applications. It combines identity logic, wallet management, and UX primitives into a single, modular framework—built for both dApp developers and protocol teams.\n\n### The Problem It Solves\n\nMost Web3 projects face three major friction points during development:\n\n1. **Lack of a standardized, developer-friendly identity layer**  \n   Developers must reinvent user identity, trust signals, and access controls for each app.\n\n2. **High onboarding friction for new users**  \n   Wallet creation, key management, and sign-in UX are still confusing for non-technical users.\n\n3. **No out-of-the-box tools to connect reputation data to access or interaction logic**  \n   Apps can’t easily integrate on-chain or off-chain verification signals into smart contracts or frontends.\n\n### Cubid SDK Solves This By:\n\n- Providing a plug-and-play system for **issuing, verifying, and displaying identity stamps**\n- Supporting **wallet connection or seedless embedded wallet creation** using a Shamir Secret Sharing scheme (2-of-3)\n- Offering **app-scoped identity**, privacy defaults, and built-in **Sybil resistance tools**\n- Exposing an easy-to-use **API and UI layer** for identity checks, stamp display, and wallet flows\n\nCubid SDK dramatically reduces dev time for apps that need wallet onboarding, user reputation, or identity-based access—freeing teams to focus on product logic instead of infrastructure.\n\nThe SDK is available at : https://www.npmjs.com/package/cubid-sdk\n\nDocs are available at: https://docs.cubid.me/#/", "hidden": false, "question": "Provide a brief overview of your tool, library, or framework. What specific problem or inefficiency in the development process does it address?", "questionId": 5}, {"type": "paragraph", "answer": "Cubid SDK helps Web3 developers ship faster by **abstracting complex identity and wallet infrastructure** into a modular, ready-to-integrate toolkit.\n\n### Key Efficiencies:\n- **One-line embedded wallet integration**  \n  Developers can let users create app-scoped, seedless wallets without building custom key management or recovery flows. This is especially valuable for onboarding mobile and web2-first users.\n\n- **Drop-in identity and stamp APIs**  \n  Apps can query a user's verifiable credentials (stamps) and humanity score via a simple API—eliminating the need to manually build identity systems, Sybil resistance checks, or trust scoring logic.\n\n- **App-scoped identity out of the box**  \n  No need to implement custom privacy-preserving login or identity isolation logic. Cubid provides per-app identities by default.\n\n- **Interoperable by design**  \n  Developers can issue stamps that other dApps can recognize and build on, creating shared identity signals across the ecosystem with zero integration friction.\n\n### Examples:\n- DeFi protocols can use the SDK to gate governance participation based on verified Cubid stamps (e.g. human-verified, KYC-lite), saving weeks of custom logic and front-end UI work.\n- dApps can launch with Cubid's embedded wallet flow, achieving **>95%+ wallet creation success** among users unfamiliar with Web3 tools—without having to teach seed phrases or use custodial wallets.\n\n**Enhancing Security**\n\n- **Non-custodial wallet design with built-in recovery**  \n  Wallets are generated using **2-of-3 Shamir Secret Sharing**, with key shares distributed between the user’s device, the app, and Cubid’s secure manager. This improves UX **without compromising control or introducing centralized risk**.\n\n- **Privacy-first identity model**  \n  Users' real wallets are never exposed unless they opt in. All identity and wallet interactions are **app-scoped by default**, preventing tracking across apps and reducing attack surfaces.\n\n- **Passive Sybil detection tools**  \n  Cubid monitors for credential reuse and coordinated behavior across identities. This gives developers lightweight tools to **flag suspicious activity**—without needing to build complex heuristics themselves.\n\nBy combining these capabilities, Cubid gives developers the ability to build **secure, human-aware applications** without the heavy lift—accelerating development while aligning with Ethereum’s principles of decentralization, security, and user sovereignty.", "hidden": false, "question": "How does your project reduce development barriers, improve efficiency, or enhance the security of Web3 projects? Please provide specific examples or metrics if available.", "questionId": 6}, {"type": "paragraph", "answer": "Cubid has been in stealth development for two years but is a very young project. We recently went live in Jan 2025. We currently have close to 10 pilot projects building on Cubid from our v1 Beta testing. The protocol is now in v2, open for all developers to use as of March 2025.", "hidden": false, "question": "Describe the current usage and support for your tool within the developer community. This could include GitHub stars, downloads, or testimonials from developers.", "questionId": 7}, {"type": "paragraph", "answer": "Cubid has already shipped core functionality, including **identity stamps**, **embedded wallet creation**, and **developer-facing APIs**. The next stage of our roadmap focuses on expanding SDK functionality, improving developer experience, and increasing ecosystem adoption.\n\n### Q2 2025 – Cubid SDK v3 Launch (In Progress)\n- Finalize embedded wallet recovery UX (biometric flows, fallback guidance)\n- Expand stamp integrations (DAO participation, educational credentials, verified contributors)\n- Improve documentation and API reference\n- Launch tutorials and integration examples\n\n### Q3 2025 – Multi-Chain & On-Chain Identity\n- Add support for additional EVM chains (starting with Celo, Polygon, Base)\n- Enable optional **minting of Cubid identity as a soulbound NFT**\n- Launch open stamp-issuer portal and schema registry\n- Introduce developer CLI tools for local testing, stamp creation, and wallet simulation\n\n### Q4 2025 – Analytics, Trust Signals & Scaling\n- Build lightweight **trust score dashboard and query tools**\n- Add usage analytics for stamp adoption and wallet creation (opt-in)\n- Improve backend indexers for performance and multi-app scaling\n- Begin open beta for app-scoped Sybil detection APIs\n\n---\n\n**Use of Grant Funds**\n\nGrant funding will directly support:\n- **Core SDK development** (recovery, identity minting, SDK extensions)\n- **UI/UX improvements** for the embedded wallet flow and stamp components\n- **Technical documentation**, sample apps, and developer onboarding materials\n- **Chain integrations and testing** across additional EVM-compatible networks\n- **Infrastructure and indexing costs** for managing identity data across multiple apps\n\nCubid’s roadmap is designed to help other builders go faster—by offering a production-ready, privacy-respecting framework for wallets and identity. With grant support, we’ll make Cubid SDK v3 the go-to toolset for building secure, human-centered dApps in the open-source Web3 ecosystem.", "hidden": false, "question": "Outline your project's roadmap and how the grant funds will be used to achieve your development goals.", "questionId": 8}, {"type": "paragraph", "answer": "Cubid is primarily an API-based protocol in terms of interacting with dApps. While we do enable users to mint their identity on-chain in the form of Soulbound NFTs on other chains, this is not yet live on Arbitrum. As a true cross-chain protocol we are open to adding Arbitrum SBTs based on developer demand. Our current on-chain activity is limited to verifying users identities by read-only on-chain operations.", "hidden": false, "question": "For any project deploying smart contracts on blockchain networks, please list all your deployer addresses and their corresponding blockchain networks. Use this format for each entry: [deployer_address], [chain_id]—for example, 0x123abc..., 42161 (This represents a deployer address on the Arbitrum network). Please include a separate line for each unique deployer address and blockchain combination.", "questionId": 9}], "project": {"id": "0x61a0738033c9247b1236c3d0ee1cc3a098e114d8292394c57b4083ef78ab8278", "title": "Cubid Protocol", "logoImg": "bafkreiegyt3vhirpxlukw3jv6s2htumqtbzievhoo7xavj62iudnuxkx2e", "metaPtr": {"pointer": "bafkreibitlzj6rig3qucni4pgqorua7j76djttrdvssh2wz5mlmgccgfr4", "protocol": "undefined"}, "website": "https://cubid.me", "createdAt": 1743461125651, "userGithub": "KazanderDad", "credentials": {"github": {"type": ["VerifiableCredential"], "proof": {"type": "EthereumEip712Signature2021", "created": "2025-03-31T22:37:53.042Z", "@context": "https://w3id.org/security/suites/eip712sig-2021/v1", "proofValue": "0xec477010c354ae2cd4acb8e9ccd2504ba40e7f70fc7091c5037c50d889797e2e0f3151011a79204dc786d24c03fa98dd4764a5d2534b53c4b33136e1f41f55101c", "eip712Domain": {"types": {"Proof": [{"name": "@context", "type": "string"}, {"name": "created", "type": "string"}, {"name": "proofPurpose", "type": "string"}, {"name": "type", "type": "string"}, {"name": "verificationMethod", "type": "string"}], "@context": [{"name": "nullifiers", "type": "NullifiersContext"}, {"name": "provider", "type": "string"}], "Document": [{"name": "@context", "type": "string[]"}, {"name": "credentialSubject", "type": "CredentialSubject"}, {"name": "expirationDate", "type": "string"}, {"name": "issuanceDate", "type": "string"}, {"name": "issuer", "type": "string"}, {"name": "proof", "type": "Proof"}, {"name": "type", "type": "string[]"}], "EIP712Domain": [{"name": "name", "type": "string"}], "CredentialSubject": [{"name": "@context", "type": "@context"}, {"name": "nullifiers", "type": "string[]"}, {"name": "id", "type": "string"}, {"name": "provider", "type": "string"}], "NullifiersContext": [{"name": "@container", "type": "string"}, {"name": "@type", "type": "string"}]}, "domain": {"name": "VerifiableCredential"}, "primaryType": "Document"}, "proofPurpose": "assertionMethod", "verificationMethod": "did:ethr:0xd6f8d6ca86aa01e551a311d670a0d1bd8577e5fb#controller"}, "issuer": "did:ethr:0xd6f8d6ca86aa01e551a311d670a0d1bd8577e5fb", "@context": ["https://www.w3.org/2018/credentials/v1", "https://w3id.org/vc/status-list/2021/v1"], "issuanceDate": "2025-03-31T22:37:53.041Z", "expirationDate": "2025-06-29T22:37:53.041Z", "credentialSubject": {"id": "did:pkh:eip155:1:0xE757B9475e8BDabfeF5bF6b7850dFd90971bf77F", "@context": {"provider": "https://schema.org/Text", "nullifiers": {"@type": "https://schema.org/Text", "@container": "@list"}}, "provider": "ClearTextGithubOrg#Cubid-Me#98373366", "nullifiers": ["v0.0.0:mpACiXZT3p7mEm88YAhD2fg5/ppfqlgN60K7tiMcYBU="]}}}, "description": "Grant Application: CUBID Protocol – Decentralized Identity + Embedded Wallet Infrastructure for Ethereum\n\n## Project Name\n**CUBID Protocol**\n\n## Project Tagline\n**Modular, privacy-preserving identity and wallet infrastructure for the next generation of web3 apps.**\n\n## Project Description\n\n**Cubid Protocol** is a foundational layer for building **on-chain identity and wallet experiences** that are secure, composable, and developer-friendly. It provides:\n\n1. **Cubid Passport** — a decentralized identity layer where users build a persistent, stamp-based identity graph. Users collect “stamps” (verifiable credentials) tied to wallet addresses, achievements, social proofs, and real-world affiliations. This identity graph is privacy-preserving, interoperable, and portable across the Ethereum ecosystem.\n\n2. **Cubid Embedded Wallet SDK** — a flexible, app-scoped wallet system that gives developers the ability to let users:\n   - Connect an existing wallet (via WalletConnect or RainbowKit)\n   - **Create a non-custodial embedded wallet** using Shamir’s Secret Sharing (2-of-3 key management) without ever needing to save or manage a seed phrase.\n   - Share their Human-score and any associated information related to the individual stamps.\n\nTogether, these tools empower developers to **safely onboard new users, build trust-based access systems, and create meaningful web3 UX** for real people—not just power users.\n\n---\n\n## How the Project Strengthens Ethereum’s Infrastructure\n\nCubid addresses two critical needs for Ethereum’s long-term scalability and usability:\n\n### 1. **Decentralized Identity Infrastructure**\nCubid Passport is an open, composable identity layer that gives users a way to **build a persistent, cross-dapp reputation** without centralizing control. It enables:\n- Sybil resistance through composable stamps\n- Access control and governance based on identity, not just tokens\n- Verifiable humanity scores, integrations with verification providers like GoodDollar, BrightID, Idena, etc.\n- Trust scoring for DAOs, marketplaces, and reputation-based apps\n\n**It helps Ethereum move beyond wallet = user, and toward identity = user.**\n\n### 2. **User-Owned Wallet Infrastructure**\nThe Cubid Embedded Wallet SDK gives developers a robust toolkit to onboard users who:\n- Don’t have wallets\n- Don’t want to deal with seed phrases or custody complexity\n- Are coming from web2 or mobile-first environments\n\nUsing a **2-of-3 Shamir Secret Sharing approach**, Cubid creates non-custodial app-scoped wallets where:\n- One key share is stored locally on the user’s device\n- One is encrypted and stored by the app\n- One is stored securely via the Cubid secret manager\n\nThis system supports **account recovery, app-scoped control, and UX upgrades**—all while remaining fully trustless and private.\n\n---\n\n## Open Source Commitment\n\nCubid is fully open-source and committed to the core values of Ethereum: decentralization, privacy, sovereignty, and modularity.\n\n- Code is published under a permissive open-source license\n- All SDKs and smart contracts are documented and available for developers to fork, extend, or build with\n- The project is community-aligned and welcomes contributors, audits, and public feedback\n\n---\n\n## Core Contributions to the Ethereum Ecosystem\n\n- **Identity Layer**: Provides a portable, verifiable on-chain identity stack to replace centralized authentication or siloed logins\n- **Wallet Onboarding**: Reduces friction for new users and mobile-first flows, helping Ethereum scale beyond experienced users\n- **Privacy-Preserving Key Management**: Supports seedless wallet creation without compromising custody or sovereignty\n- **Sybil Resistance & Reputation**: Enables new forms of access control, voting, and community trust on Ethereum\n- **Developer Tooling**: Provides plug-and-play SDKs for dApps and DAOs to integrate identity, wallets, and access layers with minimal setup\n\n---\n\n## Alignment with Grant Round Priorities\n\nThis proposal aligns with the goals of the Ethereum Infrastructure Round in the following ways:\n\n- **Decentralized Identity**: Cubid Passport directly enhances Ethereum’s ability to manage user identity in a decentralized, interoperable way.\n- **User Experience & Onboarding**: Cubid Embedded Wallet SDK reduces onboarding complexity and makes web3 more accessible to the next billion users.\n- **Privacy & Security**: The 2-of-3 Shamir-based key splitting approach provides strong user protection without introducing centralized custody or insecure recovery flows. \n- **Privacy & Security**: Users are in full control of what information to share or not share with any dApp.\n- **Open Source Infrastructure**: All components are open-source, modular, and permissionless to adopt.\n\n---\n\n## Roadmap (Next 3–6 Months)\n\n- Launch v2 of the **Cubid Embedded Wallet SDK** with improved support for app-scoped wallets, better recovery UX, mobile-first flows, and enhanced management of Blacklisted vs. Greylisted stamps (=Sybil attacks)\n- Expand **Cubid Passport** integrations with additional verification providers, DAOs, and access-controlled apps\n- Publish detailed **developer documentation and onboarding guides**\n- Release **stamp explorer UI** and dashboard for users to manage identity across apps\n- Begin outreach and integration partnerships with builders in identity, gaming, social, DeFi, and coordination tooling\n\n---\n\n## Success Metrics\n\n- **10+ dApps integrating Cubid SDKs** within 6 months\n- **5,000+ Cubid Passports created**, with active stamps\n- **3+ integrations using Cubid humanity score or stamps for access or governance**\n- **500+ embedded wallets** created without seed phrases\n- Community contributions to the SDK, UI, or core contracts\n\n---\n\n## Team & Contributors\n\nCubid is being built by a small, experienced team of Ethereum-native developers, privacy advocates, and UX designers. The project is independently developed and self-funded to date, with a track record of open-source contributions and identity-focused infrastructure work. We are now seeking support from the Ethereum community to accelerate development and scale adoption.\n\n---\n\n## Funding Use\n\nFunding from this round will support:\n\n- Core protocol and SDK development\n- Wallet recovery flow implementation\n- UI and dashboard tooling for identity management\n- Developer documentation, testing, and deployment\n- Ecosystem integrations and partnerships\n\n---\n\n## Closing\n\nCUBID Protocol is building core identity and onboarding infrastructure that **Ethereum needs to reach real users at scale**. By combining modular identity with embedded wallets, Cubid gives developers the power to build safer, smarter, and more human-centered experiences—without compromising the principles Ethereum stands for.\n\nWe’re excited to contribute this layer to the ecosystem and welcome your support.\n", "lastUpdated": 0, "projectGithub": "Cubid-Me", "projectTwitter": "CubidProtocol"}, "recipient": "0xE757B9475e8BDabfeF5bF6b7850dFd90971bf77F"}}