{"signature": "0x39ef0af55dd17606e10f899d40fe0af6590c7795e5c559fb37301de71d5f00dd4722848b050e16b79d350a079e06bffe297260c6714996b9acbddc263f7595a51b", "application": {"round": "0x145052E87140b7309F6EE18Ba12fC187560d5D89", "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 to prior rounds.", "questionId": 4}, {"type": "paragraph", "answer": "We contribute to the Ethereum network's infrastructure in several ways. \n\nIdentity Layer: Provides a portable, verifiable on-chain identity stack to replace centralized authentication or siloed logins\n\nWallet Onboarding: Reduces friction for new users and mobile-first flows, helping Ethereum scale beyond experienced users\n\nPrivacy-Preserving Key Management: Supports seedless wallet creation without compromising custody or sovereignty\n\nSybil Resistance & Reputation: Enables new forms of access control, voting, and community trust on Ethereum\n\nDeveloper Tooling: Provides plug-and-play SDKs for dApps and DAOs to integrate identity, wallets, and access layers with minimal setup\n\nYou can find our SDK here: https://www.npmjs.com/package/cubid-sdk\n\nDocs are here: https://docs.cubid.me/", "hidden": false, "question": "How does your project contribute significantly to the Ethereum network's infrastructure? Please provide specific examples and metrics if available.", "questionId": 5}, {"type": "paragraph", "answer": "Cubid introduces several novel approaches that push the Ethereum ecosystem forward, particularly in the areas of privacy-preserving identity, wallet abstraction, and interoperable UX primitives.\n\n1. Seedless, App-Scoped Non-Custodial Wallets\nCubid’s Embedded Wallet SDK offers a unique approach to wallet onboarding by using Shamir’s Secret Sharing (2-of-3 split) to eliminate the need for seed phrase backups. This enhances:\n- Privacy & Security: Users never need to write down or expose a full private key. Each key share is stored separately—on the device, encrypted in-app, and with Cubid’s secure backup manager.\n- User Experience: Users can onboard instantly using fingerprint or device-based auth, without friction or prior web3 knowledge.\n- Developer Control: App-scoped wallets make it possible to provide users with dedicated identity and signing contexts per app, improving UX and compartmentalization.\n\nThis approach balances non-custodial architecture with real-world usability, especially for mobile-first and mainstream users.\n\n2. Composable Identity via Stamp Graphs\nCubid Passport introduces a new model of on-chain, composable identity where users collect “stamps” — verifiable credentials tied to their activity, achievements, or affiliations. These stamps:\n- Can originate from both on-chain and off-chain sources\n- Are interoperable across dApps, communities, and governance tools\n- Feed into Sybil resistance, access control, and social reputation models\n\nRather than relying on one single-proof identity provider or protocol, Cubid offers a modular identity graph that users fully control, making it one of the first implementations of truly composable and portable identity on Ethereum.\n\n3. Interoperable SDKs for dApp Builders\nBoth the identity layer (Passport) and wallet layer (Embedded SDK) are built to be fully modular, developer-friendly, and open-source. Developers can:\n- Integrate one or both components with minimal code\n- Extend the SDKs for new use cases (e.g., DAO voting, G$ claiming, private communities)\n- Use as drop-in UI components or raw APIs\n\nThis supports interoperability at the developer layer, enabling any Ethereum-based app to plug in human-first UX features without reinventing identity or wallet onboarding.", "hidden": false, "question": "Describe any pioneering development work in your project, particularly in enhancing privacy, interoperability, or user experience.", "questionId": 6}, {"type": "paragraph", "answer": "Cubid addresses two persistent challenges in the Ethereum ecosystem:\n(1) Identity and reputation fragmentation, and\n(2) High-friction onboarding and wallet management for mainstream users.\n\n1. Decentralized Identity & Reputation Fragmentation\nThe Problem:\nEthereum lacks a standardized, user-owned identity layer. Most dApps treat wallet addresses as users, which leads to:\n\nWeak Sybil resistance\n\nNo portable trust or reputation between applications\n\nInability to meaningfully gate experiences or governance based on user behavior or social proof\n\nCubid’s Solution:\nCubid Passport introduces a modular, interoperable system where users build identity through verifiable “stamps” (credentials) tied to achievements, affiliations, or proofs. This creates:\n\nA composable identity graph usable across dApps\n\nImproved Sybil resistance through multi-source verification\n\nNew UX primitives like trust-weighted voting, identity-gated access, and reputation-based rewards\n\nCubid improves on existing alternatives like ENS or POAP by combining verifiable credentials, privacy, and human-first identity scoring in a single, developer-friendly protocol.\n\n2. Wallet Onboarding & User Experience\nThe Problem:\nMost Ethereum wallets rely on seed phrases, complex UX, and assume technical literacy. This is a significant barrier to adoption, especially for mobile-first or mainstream users.\n\nCubid’s Solution:\nCubid’s Embedded Wallet SDK allows dApps to offer users two choices:\n\nConnect with WalletConnect or RainbowKit\n\nOr create a non-custodial embedded wallet using Shamir’s Secret Sharing (2-of-3), with:\n\nOne key share stored on-device\n\nOne encrypted share stored by the dApp\n\nOne securely stored by Cubid’s key manager\n\nThis enables seedless, app-scoped wallet creation with optional biometric recovery—dramatically improving onboarding and retention without sacrificing self-custody or security.\n\nCompared to existing “smart wallets” or custodial options, Cubid delivers a non-custodial, privacy-preserving solution that still feels familiar to web2 users.", "hidden": false, "question": "What specific problems or challenges in the Ethereum ecosystem does your project address? How does your solution improve upon existing alternatives?", "questionId": 7}, {"type": "paragraph", "answer": "Roadmap for the next 3–6 Months:\n\nLaunch v2 of the Cubid Embedded Wallet SDK with enhanced support for app-scoped wallets, improved recovery UX, and mobile-first flows\n\nExpand Cubid Passport integrations with additional verification providers, DAOs, and access-controlled apps\n\nPublish detailed developer documentation and onboarding guides\n\nRelease stamp explorer UI and dashboard for users to manage identity across apps\n\nBegin outreach and integration partnerships with builders in identity, gaming, social, DeFi, and coordination tooling", "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 enhances Ethereum’s decentralization and security by introducing a modular identity and wallet layer that is private by default, user-controlled, and designed to scale trust without compromising sovereignty. It tackles key weaknesses in identity handling, onboarding, and Sybil resistance—foundational issues for a secure and inclusive Ethereum ecosystem.\n\n1. Decentralized, App-Scoped Identity (No Global Logins)\nCubid lets users create and manage verifiable identities that are app-scoped by default. This means:\n- dApps only see a unique Cubid identity tied to their app—not the user’s wallet or global activity.\n- Users can build identities across multiple wallets, not just one.\n- Wallets are only linked or exposed if the user explicitly opts in to share them.\n\nThis breaks the assumption that a wallet = user, and offers true contextual privacy for web3. Users maintain control, and Cubid acts as a reputation layer—not a surveillance layer.\n\n2. Private, Non-Custodial Wallet Infrastructure\nThe Cubid Embedded Wallet SDK enables secure wallet creation without seed phrases or centralized custody. Through a 2-of-3 Shamir’s Secret Sharing scheme, users:\n- Create wallets that they control—but don’t have to back up manually.\n- Gain secure recovery mechanisms without sacrificing decentralization.\n- Can generate one wallet per app, further enhancing privacy and reducing linkability.\n\nThis infrastructure supports web2-style UX without introducing centralized risks or giving up custody.\n\n3. Built-in Sybil Detection and Resistance\nCubid constantly monitors for Sybil behavior and credential reuse across apps, using internal heuristics and network-level analysis. While identities are app-scoped, Cubid can detect:\n- Attempts to reuse credentials across multiple apps\n- Clusters of identities acting in coordination\n\nThis system works behind the scenes to flag suspicious patterns, enabling participating dApps to make trust-weighted decisions.\n\nThe more apps use Cubid, the stronger the Sybil resistance becomes—a network effect that improves Ethereum’s trust infrastructure over time.\n\n4. Permissionless, Open, and Sovereign by Design\n- Cubid is fully open-source and developer-friendly.\n- All identity logic is modular and app-defined—no centralized gatekeepers.\n- Users can prove reputation or humanity across apps without revealing their wallet, identity, or social accounts.\n\nIn Summary\n\nCubid helps Ethereum evolve beyond static, wallet-bound identity by providing privacy-preserving, app-scoped identity and wallet infrastructure. It strengthens the ecosystem by:\n- Decentralizing identity ownership\n- Protecting users from overexposure or tracking\n- Enabling scalable Sybil resistance\n- Supporting secure, non-custodial onboarding\n\nAs adoption grows, Cubid becomes a shared trust protocol that improves Ethereum’s resilience, composability, and user experience from the ground up.", "hidden": false, "question": "How does your project contribute to the decentralization and security of the Ethereum network?", "questionId": 9}, {"type": "paragraph", "answer": "Cubid is primarily an API-based project for dApp interactions. We read on-chain transactions rather than write them. We do have deployers for Soulbound NFTs on Ethereum and other chains, but not yet on Arbitrum.", "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": 10}], "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"}}