{"signature": "0xbc5a9908b7ea086d763d26a0ef8c191ba1e6f16286e4eb245f1ee1ede446a58852872136a4fd3eff5c6eb4984ba45a741f46f772e855f4271b2771d20e4ca9031b", "application": {"round": "0x3E93205B786796Cf7Ea70404E89c7dda3b84D07a", "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": "short-answer", "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 contributes to the growth of the open-source ecosystem by providing core identity and wallet infrastructure that is modular, permissionless, and easy to integrate into any Web3 application.** It’s designed to be a foundational layer for developers building apps with identity, reputation, or embedded wallets—especially those focused on accessibility, inclusion, and usability.\n\n### Specific Contributions:\n\n- **Cubid Passport (Decentralized Identity Layer):**\n  - Fully open-source protocol and SDK for creating, issuing, and verifying identity \"stamps\" (credentials).\n  - Any dApp can issue its own stamps, query user stamps, or build access controls based on verified identity—all without lock-in.\n  - Enables trust scoring, Sybil resistance, and community-based verification without centralized providers.\n\n- **Cubid SDK:**\n  - Open-source SDK for app-scoped, non-custodial embedded wallet creation using Shamir’s Secret Sharing (2-of-3), as well as full interaction with the Stamps of Cubid Passport.\n  - Supports both traditional wallet connections (e.g., WalletConnect) and embedded wallets, making onboarding smoother for non-crypto-native users.\n  - Designed to help other developers reduce friction and improve UX in their own dApps—especially for social impact, financial inclusion, and mobile-first use cases.\n\n- **Composable, Modular Architecture:**\n  - Developers can use Cubid’s components independently or together, and contribute new identity stamp integrations, recovery flows, or verification providers.\n  - Cubid is actively encouraging external contributions, audits, and community-maintained modules.\n\n- **Live Integrations and Real Usage:**\n  - Already being integrated by projects like GoodDollar (for verified identity stamps and claim access).\n  - Supports builders in creating verified access flows, identity-based bounties, trust scoring for DAOs, and more.\n\n---\n\nBy lowering the barriers to building secure, human-centered apps and offering plug-and-play modules for decentralized identity and wallets, Cubid expands what’s possible for developers in the OSS ecosystem—and helps move the broader Web3 space toward inclusion, usability, and self-sovereignty.", "hidden": false, "question": "How does your project contribute to the growth of the OSS ecosystem? Please provide specific examples of how your application enhances or expands the current ecosystem.", "questionId": 5}, {"type": "paragraph", "answer": "Cubid offers a unique combination of **decentralized identity infrastructure** and **embedded wallet tooling**—packaged as an open-source SDK and dApp framework. It’s designed to help developers build apps that are **more human-aware, privacy-preserving, and accessible** to non-crypto-native users.\n\n### Key Features:\n\n- **Embedded Wallet Creation**\n  - Seedless, non-custodial wallets generated using Shamir’s Secret Sharing (2-of-3).\n  - No need for users to manage private keys or seed phrases.\n  - App-scoped by default for enhanced privacy and contextual identity.\n\n- **Third-Party Wallet Support**\n  - Out-of-the-box support for WalletConnect and RainbowKit for users with existing wallets.\n\n- **Decentralized Identity Stamps**\n  - Users collect verifiable “stamps” tied to credentials, affiliations, achievements, or social proofs.\n  - Apps can issue their own stamps or verify existing ones to gate access, build trust layers, or power Sybil resistance.\n\n- **Humanity Score**\n  - An aggregated score based on a user’s stamps and reputation data, useful for DAO voting, community moderation, and impact assessment.\n\n- **App-Scoped Identity Sharing**\n  - By default, users share a unique Cubid identity with each app—**no cross-app wallet exposure**, unless explicitly opted-in.\n  - This improves privacy while enabling app-specific reputations to form.\n\n- **Sybil Detection Layer**\n  - Cubid runs background analysis to detect suspicious behavior or stamp reuse across apps—strengthening trust as adoption grows.\n\n---\n\n**What Differentiates Cubid**\n\nCubid is the **only protocol offering a unified solution** for both **identity** and **wallet onboarding** that is:\n- **App-scoped by default** (privacy-focused, unlike ENS or global profiles).\n- **Non-custodial, seedless, and developer-friendly** (unlike most onboarding SDKs).\n- **Composable and open-source**, letting developers adopt just the identity layer, just the wallet tools, or both.\n- **Designed for inclusion**, enabling apps to onboard users with zero crypto knowledge.\n\nWhether you’re building a social dApp, DAO tool, learning platform, or DeFi experience, Cubid gives you plug-and-play primitives to manage **who users are**, **how they show up**, and **how they interact**—all without central control or user friction.", "hidden": false, "question": "What features or use cases does your dApp/App present? How is it differentiated?", "questionId": 6}, {"type": "paragraph", "answer": "Cubid has already shipped its core infrastructure, including the **Cubid SDK**, **embedded wallet tooling**, and the **Cubid Passport stamp system**. We’re now preparing for the next phase of development—focused on deepening functionality, improving UX, and expanding cross-chain and on-chain capabilities.\n\n### Upcoming Development (SDK v3 and Beyond)\n\n1. **Improved Wallet Recovery UX**  \n   We’ll enhance the embedded wallet recovery flow with better user guidance, mobile-native experiences, and biometric options (e.g. Face ID, fingerprint) where supported.\n\n2. **Expanded Stamp Library**  \n   We plan to issue and integrate more high-signal identity stamps (e.g., proof of DAO participation, off-chain verifications, attestations from trusted apps) to grow utility across Web3 use cases.\n\n3. **On-Chain Identity Minting**  \n   Enable **minting of Cubid identity as a soulbound NFT**, optionally app-scoped or cross-app, giving users a portable, on-chain representation of their reputation and verified status.\n\n4. **Multi-Chain Expansion**  \n   Extend support for additional EVM-compatible chains and L2s, improving access for developers and users across ecosystems.\n\n5. **UX/UI Improvements**  \n   Enhance both developer and end-user experiences, including simplified SDK integration, onboarding flows, and in-app display components for stamps and identity scores.\n\n6. **Security Audits & Infrastructure Scaling**  \n   Allocate funds toward smart contract and key management audits, and optimize backend infrastructure for scaling usage across apps and chains.\n\n### Use of Grant Funds\n\nGrant funding will go directly toward:\n- Development of SDK v3 and infrastructure improvements  \n- UX design and implementation  \n- On-chain identity minting logic and contract work  \n- Cross-chain deployment and testing  \n- Documentation, tutorials, and developer onboarding resources\n\nBy supporting Cubid, this grant will help advance the **identity and onboarding layer** for Ethereum—making it easier for builders to create trust-based, user-friendly applications that scale across use cases and networks.", "hidden": false, "question": "What are your plans for further development, and how will the grant funds be used to achieve these goals?", "questionId": 7}, {"type": "paragraph", "answer": "Cubid is primarily an API-based tool when it comes to dApp interactions. We read information from on-chain data to validate user information, but rarely write. (In some cases users opt to write their identity on-chain as a soul-bound token, which we support, but have not enabled Arbitrum for this yet.)", "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": 8}], "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"}}