{"signature": "0x1e4279b244cce34ffbae7ec1d2b55a727104b64cd11460d0c730fa859cae9bc9325c083a1ddd36dbf498af73df300b35f75b7bae829e98a8a22fd099b3d0f70c1b", "application": {"round": "0xe03a19f4921d69cddd37f54dfe814dc66aa92100", "answers": [{"type": "email", "hidden": true, "question": "Email Address", "questionId": 0, "encryptedAnswer": {"ciphertext": "nyedBafsilQ2hgYfhlxcBFqEc331QCcjFgOjCjBTNw6FiNVgWv5A59OeSMW0Dwzq", "encryptedSymmetricKey": "83d2135b665a3417d50c4564715a856f116177e17cbec5fe854c7bd02412db568973759251c31bc31fb7dbb3fa7b820aca047b815c21b616239526a7325d63f500bcc38872430113407d7b531a9ca661a78ccfd45d371667cc9598bb6767378284a5aa24f858841df61ad727e9970538dbf770c074c5e9e1fd11f3b5b2cb209d0000000000000020309e8b9409ea715a54a6e46a55483c770c08317254be294afc1e3780357cf0295942b77699aabe11d72dc0f5add29a8b"}}, {"type": "short-answer", "hidden": true, "question": "Telegram Handle We Can Use To Contact You(you can answer N/A)", "questionId": 1, "encryptedAnswer": {"ciphertext": "11zJorwpTKA5DCkUayau6mqpoOzjknD+8+67Om11Uik=", "encryptedSymmetricKey": "cf6809fb6a1e463adcc244377eb63cf0ba90bcf6b8677cd317c4037be0a9c6b8e873b615f4d1ef82ef458ae331684e02de0ff0305e61f3a4128faa83db5a313d04dafecaa495d0982859cf8dbe4fab70852781bd6e1c54c7b0c30f6efd2ca8a75c8e4c4980bce097a7ab2bb9bac6dfb814ca3f563d7400b685ec72bb94185ad50000000000000020474b0e6eef72d60c9814ef4aeecef6135c39f6f27587057c3226e15c0281051329f16f4dee5cbd4f5421023de13565ae"}}, {"type": "link", "answer": "https://github.com/dm3-org/dm3", "hidden": false, "question": "Project GitHub Repo (Not Team Page): ", "questionId": 2}, {"type": "number", "answer": "5", "hidden": false, "question": "Total Team Size", "questionId": 3}, {"type": "paragraph", "answer": "https://github.com/AlexNi245 - alex245.eth\nhttps://github.com/malteish - malteish.eth \nhttps://github.com/steffenkux - stkux.eth", "hidden": false, "question": "List the Github Handles and Wallet Addresses of Each Team Member (e.g. owocki - 0x123, kbw  - 0x456):", "questionId": 4}, {"type": "paragraph", "answer": "https://twitter.com/SteffenKux\nhttps://twitter.com/AlexNi245\nhttps://twitter.com/vegaypatino\nhttps://twitter.com/TheMayCas\nhttps://twitter.com/AlexNi245", "hidden": true, "question": "Social profiles (Twitter, Farcaster, Lens, etc.) of other main team members publicly associated with the project (N/A for solo founders): ", "questionId": 5}, {"type": "link", "answer": "https://t.me/dm3protocol", "hidden": false, "question": "Link to your Public Group Chat (e.g. Discord or Telegram)", "questionId": 6}, {"type": "paragraph", "answer": "-We have finished all milestones regarding OP Governance Grant, and publish it for public use in the OP ecosystem. \n\n-We have finished the integration with Genome project, the domain service for Gnosis. \n\n-We have provided the infrastructure for any Gnosis chain project to make use of our protocol. \n\n-Created an Arbitrum resolver. \n", "hidden": false, "question": "If you've participated in past grant rounds, please share any new updates or milestones from the prior months (N/A if you haven\u2019t participated previously). ", "questionId": 7}, {"type": "address", "hidden": true, "question": "If you participated in past grant rounds using a different project payout wallet address, please share it here:", "questionId": 8}, {"type": "paragraph", "answer": "https://github.com/dm3-org/dm3", "hidden": false, "question": "Where should we look to see the impact of your project? Please provide links to public websites and/or the latest values for key metrics you track privately. This might be used in future impact reports", "questionId": 9}, {"type": "paragraph", "answer": "RetroPGF 2 2023 & 3 2024, Governance Fund 2023: 250,000 USD\nGnosis 2024: 30,000\nENS DAO + ENS Hackathons 2023: 40,000\nSelf funding: 100,000\n", "hidden": false, "question": "Total Prior Funding Amounts, Sources, and Dates for the project in USD", "questionId": 10}, {"type": "checkbox", "answer": ["Grants", "VC"], "hidden": false, "question": "Which of the following funding sources do you have? Check all that apply", "questionId": 11}, {"type": "number", "answer": "18", "hidden": false, "question": "How old (in Months) is the project?  ", "questionId": 12}, {"type": "multiple-choice", "answer": "Europe", "hidden": false, "question": "Location/Region where the project is based ", "questionId": 13}, {"type": "multiple-choice", "answer": "Yes", "hidden": true, "question": "Have you read and confirmed your grant abides by the Program General Eligibility Policy? ", "questionId": 14}, {"type": "short-answer", "answer": "No", "hidden": true, "question": "Are you applying for any other OSS rounds in GG20? (Reminder: you can only be accepted into one) ", "questionId": 15}, {"type": "paragraph", "answer": "Currently, there is no fully web3-based, scalable, and interoperability-focused messaging core protocol for Ethereum or l2s and even less one that brings the identity protocols as a core piece of the infrastructure. We can provide solutions not only for the entire web3 ecosystem but also custom-made solutions for dApps that require custom-made messaging and identity management such as gaming, NFT and general social dApps. With the DM3 embedded components, secure and interoperable messaging can be added easily to dApps.\nInteroperability is a main target of the DM3 protocol which means that applications can connect to messaging solutions. Published communication profiles (DM3 profiles) are accessible on any other solution which is also DM3 interoperable.\n", "hidden": false, "question": "Please describe your dApp or App, focusing on its innovative utility or service within the ecosystem. Highlight the problem it solves or the need it addresses.", "questionId": 16}, {"type": "paragraph", "answer": "We are using ENS (other domain provider can be use too) as a general registry for DM3\u2019s communication profiles (containing public keys for encryption and signatures, and delivery information). By using CCIP (EIP3668), any sources of layer 2's, other chains, and even cloud services can be integrated into ENS, making the DM3 protocol chain-agnostic. The DM3 core protocol defines a peer-to-peer messaging protocol. Embeddable components allow dApps to integrate messaging functions as easily as one line of code. This can be used for instance as wallet-to-wallet messaging, as an integrated messenger in gaming apps, etc. ", "hidden": false, "question": "Describe how your application improves user experience in the Web3 space. Include any specific design choices or features that enhance accessibility and practical utility.", "questionId": 17}, {"type": "paragraph", "answer": "Many social channels and communications can be censored, our protocol allow a basic human right, which is communication, to happen without the risk of being censored or intercepted.", "hidden": false, "question": "In what ways does your project contribute to financial inclusion, education, or social impact? Explain the specific areas of impact and the target audience or communities you serve.", "questionId": 18}, {"type": "paragraph", "answer": "BSD 2-Clause License", "hidden": false, "question": "What type of open source software (OSS) license(s) do you have? Is all of your code available on public repos or is some portion of your codebase private?", "questionId": 19}, {"type": "paragraph", "answer": "We are fully deployed, currently working on making our full suite available in many chains as possible.\n\nFull roadmap can be seen here: https://drive.google.com/file/d/1BYXhNOp4wZyiMUz2VU335BC4G5fHI_wg/view\n", "hidden": false, "question": "What stage of development is your application currently in, and what are your immediate next steps? Provide a roadmap or development timeline if available.", "questionId": 20}, {"type": "paragraph", "answer": "- Specification and Implementation of the DM3 group chat protocol extension.\n\n-Integration guide. Based on the DM3 embedded components, messaging functionality can be added to wallets, dApps, \u2026, The integration guide describes how to use these components. \n\n-Integrate Arbitrum as Storage for DM3 profiles (SDK and Reference Implementation)\n\n", "hidden": false, "question": "How would funding from this round support your project's development and goals? Outline specific areas where the funds would be allocated (e.g., development, user research, community building).", "questionId": 21}, {"type": "paragraph", "answer": "DM3 is designed as a public good and open-source. Development is currently being coordinated by dm3.org GmbH, which is based in Germany. It is currently in the process of being transformed into a non-profit gGmbH.", "hidden": false, "question": "Anything else you'd like to share about your project, previous work, or other project affiliations? Anything you'd like to add that may help in determining project eligibility?", "questionId": 22}, {"type": "multiple-choice", "answer": "Yes", "hidden": true, "question": "Would you like to opt-in to future messages from Gitcoin for updates, information, and/or interviews? ", "questionId": 23}, {"type": "multiple-choice", "answer": "Yes", "hidden": true, "question": "Would you like to opt-in to us sharing your information with select third-parties for investment opportunities? ", "questionId": 24}], "project": {"id": "0x1887e83ef45a249378281ffcddcf692ec0d29e177a4391f398db7e6ff6c5af6b", "title": "dm3 protocol - the interoperability initiative ", "logoImg": "bafkreiapdiauiaywqf6icaivuayqdshadq3h32v3s63ulzg6ebcroijx2i", "metaPtr": {"pointer": "bafkreicavpao7vhtu7biwupdmsxzbppxwggnxikpmqtfxgfwavpqo7ngbq", "protocol": "undefined"}, "website": "https://dm3.network", "bannerImg": "bafkreiaysck5wrm52em5o7xps6myzbyl3bay6x7czzndifyxnxvgowhsxu", "createdAt": 1682070718184, "userGithub": "corpus-io/dm3", "credentials": {"github": {"type": ["VerifiableCredential"], "proof": {"jws": "eyJhbGciOiJFZERTQSIsImNyaXQiOlsiYjY0Il0sImI2NCI6ZmFsc2V9..zE8dVLleZZjaDfMpNe3MKMOBtsNr1EJq85bGtbEeX11yk6vNdTZM_Z6WKW0aAPbEPDN_gG4frqhqndJSMWMFAQ", "type": "Ed25519Signature2018", "created": "2023-08-11T19:45:38.772Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC#z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC"}, "issuer": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC", "@context": ["https://www.w3.org/2018/credentials/v1"], "issuanceDate": "2023-08-11T19:45:38.771Z", "expirationDate": "2023-11-09T19:45:38.771Z", "credentialSubject": {"id": "did:pkh:eip155:1:0x1d921dff757610FbDB0073479e12c0a07d382677", "hash": "v0.0.0:eJt9JJiJJUNnmlqP7WngA2n18mvDmMvrzLuHA4odelw=", "@context": [{"hash": "https://schema.org/Text", "provider": "https://schema.org/Text"}], "provider": "ClearTextGithubOrg#corpus-io#74208366"}}, "twitter": {"type": ["VerifiableCredential"], "proof": {"jws": "eyJhbGciOiJFZERTQSIsImNyaXQiOlsiYjY0Il0sImI2NCI6ZmFsc2V9..XS31m_LIzIyUCk-u5DcFnvmWv2ibU__uGp1hmaCvWRSZh4N9GlYsS9xYXDF9bSQd_auPOOacdlqaku4T9vZsCQ", "type": "Ed25519Signature2018", "created": "2023-08-15T16:41:28.017Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC#z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC"}, "issuer": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC", "@context": ["https://www.w3.org/2018/credentials/v1"], "issuanceDate": "2023-08-15T16:41:28.017Z", "expirationDate": "2023-11-13T16:41:28.017Z", "credentialSubject": {"id": "did:pkh:eip155:1:0x1d921dff757610FbDB0073479e12c0a07d382677", "hash": "v0.0.0:bJr+OmTapmyFUdrw6wPRwZOJjOdhFDNCEHEivS6XprA=", "@context": [{"hash": "https://schema.org/Text", "provider": "https://schema.org/Text"}], "provider": "ClearTextTwitter#dm3protocol"}}}, "description": "The dm3 protocol is a lightweight messaging protocol based on web3 technology, with a focus on secure end-2-end encryption, decentralization, scalability, and interoperability. The core of the protocol is a registry (dm3-registry) for the relevant communication information such as public keys for encryption and signatures and delivery information. Messages are delivered via a decentralized network of delivery service nodes that serve as a message cache or gateway to another messaging protocol or service.\n\nThe dm3 registry is based on ENS, i.e. the dm3 profile is added as a text record to the ENS name.\n\nThe aim of dm3 is to suggest a common base standard for web3 messaging, on which further protocols and applications can be built to create a silo-free, secure, self-determined, decentralized messaging ecosystem - based on web3 technology.\n\nThis allows users not only to have full control over their data and messages but also to choose the messaging app that best suits their needs and preferences, without the compromise of being limited to a particular ecosystem.\n\nTo achieving the goal of building a messaging standard we have launched the Interoperability Initiative: a welcoming invitation to other messaging protocols, dApps and users to integrate dm3 protocol in order to achieve interoperability regardless of your app/protocol of choosing. \n\nOur protocol is open source and we aim to build with the web3 community, so feedback is welcome!\n\nWe share constant updates on the ENS Forum:  https://discuss.ens.domains/t/standardization-web3-messaging/15182/11\n\nOur latest presentation in EthPorto: https://watch.ethporto.org/session/sessionhowtogetridof10differentmessengerappsfromyoursmartphone \n\nOur latest implementation: https://dm3.readthedocs.io/en/doc-latest/index.html\n\ndApp: https://app.dm3.network/\n\nPOC: https://t.me/vegayp\n\nThanks for reading to this point! \n\n", "lastUpdated": 0, "projectGithub": "corpus-io", "projectTwitter": "dm3protocol"}, "recipient": "0x11Ee133A1408FE2d7c62296D7eB33F234b774503"}}