{"signature": "0x842ef8c5ac8edb9ac99c71d203f26d6051859bb41da43d3c15ba1ec80fdc99390f3621415443525f38a68617873ea187d03b55d4e3d8dcfdc90bdd6db2d115e51b", "application": {"round": "0xe03a19f4921d69cddd37f54dfe814dc66aa92100", "answers": [{"type": "email", "hidden": true, "question": "Email Address", "questionId": 0, "encryptedAnswer": {"ciphertext": "RK6BAHAVKhza4D8DvnciurnGyZGnJv8ZGnLkFWwWmUYdBZ3xtvE6MjK0jb1bC/TS", "encryptedSymmetricKey": "a29653e740b968f47d6622f167db19751c68a96b151052c4fe9ff2cd944999d84b93d74b4948f26fd73219ecbaefd709d7ee2ced0eadfa6dc10a6cfe2fdc8588f0027301c1b51065be270a6314eb81c85f44ed3bf4ed8180acc14ede8cc8de8e88047a08a749968be48f98c4a5be89fcd3af12da98998eb1013822fa7f1b39200000000000000020405af0993ebd5c88c6b2f61a39ea2445fb5c425a731a6d82032888a136510326820bb26731c677988451963b1f8b3880"}}, {"type": "short-answer", "hidden": true, "question": "Telegram Handle We Can Use To Contact You(you can answer N/A)", "questionId": 1, "encryptedAnswer": {"ciphertext": "vs5smTDvlQkRP81qmwqV9p9YG98xZuQfOu8IX9C89Zc=", "encryptedSymmetricKey": "0977f4d251fefe6cca1fd2b14787cebe1640323f61a0e9d27dfcd5561437ebeca43a16d0b7183116ca8b3451766a4311ec7c3fb37aa3af4c54adc069886af7645c351fe6c9b84906a1a28b7c8637ed681b6a3ad0a1777482f47efea526e2fe8c56c336a249d45a9c32ac392b76bb56be2c8e2ba0209f7904d0fe29b4cca2dd4300000000000000207a0f16d96c936507e94f6fa37f3b47a2df116a1261456aecca3a1db5d3cfae07b4d3001b973d3ab39ce03495fcc834b6"}}, {"type": "link", "answer": "https://github.com/thenamespace", "hidden": false, "question": "Project GitHub Repo (Not Team Page): ", "questionId": 2}, {"type": "number", "answer": "4", "hidden": false, "question": "Total Team Size", "questionId": 3}, {"type": "paragraph", "answer": "- nenadmitt - artii.eth\n- branzinho - branz.eth\n- UrosZigic - uroszigic.eth\n- thecaphimself - thecap.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": "## Cap\n- Twitter: @thecaphimself\n- Warpcast: @thecap.eth\n- Warpcast channel: /namespace", "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://discord.gg/XXr9tRGup3", "hidden": false, "question": "Link to your Public Group Chat (e.g. Discord or Telegram)", "questionId": 6}, {"type": "paragraph", "answer": "N/A", "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": "We are currently building our Dashboard that will show our entire platform activity.\n\n# So far we have the following\n\n## Offchain subnames\n- gotid.eth - issued ~30 subnames\n- gotframed.eth - issued ~3,000 subnames\n- crowned.eth - issued ~4,500 subnames\n\ngotframed.eth and crowned.eth are issued through Farcaster frames that we started supporting a few days ago.\n\n# L1 subnames\n### Goerli and Sepolia testnet\nThis was done in the development phase before we launched on the mainnet.\n\n- Number of unique listed ENS names: ~100.\n- Number of minted Subnames: ~200\n- Total volume generated: ~23 ETH \n- Average spend per wallet for minting: 0.07 ETH\n- Average earning: 0.14 ETH\n\n### Mainnet\nConsidering we launched on the mainnet recently, and the gas prices have been $50+ for minting ever ince, we saw little traction among users. \n\n- Number of unique listed ENS names: 9\n- Number of minted Subnames: 11\n- Total volume generated: 0.044 ETH\n- Average spend per wallet for minting: 0.004\n\n# Integration/Partnership\nAs our mission is to democratize access to ENS and Web3 identity and make ENS available and accessible everywhere, we also track integrations and partnerships that eventually lead towards the increased use of Namespace's platform or our API and to that extent ENS as well. Therefore, we build for both consumers and developers. \n\n### Web3js integration: \nAnyone using the Web3js library can now easily implement:\n- ENS domain registration\n- text record management\n- address and name resolution\n\n Announcement post: https://twitter.com/namespace_eth/status/1770461554800247166 \n\nLink to the plugin: https://www.npmjs.com/package/@namespace-ens/web3-plugin-ens\n\n### Pending integrations:\nQuickNode and Tatum \n\n# Other\nWe are talking to many different wallets, games, and communities primarily about integrating ENS and issuing subnames to their users.", "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": "As one of the 9 official ENS Service Providers received 200k USDC from ENS Foundation to continue our work with Namespace.\n\nThis is a monthly streaming grant we started receiving in January 2024.\n\n\n", "hidden": false, "question": "Total Prior Funding Amounts, Sources, and Dates for the project in USD", "questionId": 10}, {"type": "checkbox", "answer": ["Grants"], "hidden": false, "question": "Which of the following funding sources do you have? Check all that apply", "questionId": 11}, {"type": "number", "answer": "24", "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": "Namespace is a platform and developer toolkit built to streamline ENS adoption and enhance its utility by building innovative ways ENS name owners can seamlessly issue (sell or gift) and manage Subnames. \n\nAs a platform, we provide the most comprehensive suite of tools and features for ENS name owners to get the most out of their ENS names. We allow different price customizations for selling subnames, whitelisting options, subname reservations, token-gated subname minting, etc. \n\nWhether ENS name owners are communities, wallets, games, or individuals looking to onboard people to crypto and equip them with ENS-based digital identity, we provide the most user-friendly platform that requires no technical skills and that anyone can use. \n\nFurthermore, we also build our developer documentation for more customized integrations (wallets, games, DAOs, infra providers, etc.)", "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": "When we talk about Web3 space in general, the criticism we hear the most often is that UX/UI needs to improve. Specifically around 0x addresses. We truly believe that we are heading towards the future where there are no more 0x addresses. They will be replaced by human-readable form of decentralized identifiers. \n\nDigital identity is undergoing a silent revolution that many are currently overlooking. The importance of Web3 domain and identity services such as ENS, which are at the heart of it all, is increasingly important. \n\nThat said, the fact that we are working on making ENS names and subnames available, accessible, and easily usable for everyone, everywhere, we are directly participating towards improving the overall user experience in web3. Humanizing 0x wallet addresses and giving them a name. And introducing web3 identity as one of the most important layers of the new internet. \n\nFurthermore, no decentralized application in the entire world that, currently offers a more detailed set of features for customizing issuing ENS Subnames than Namespace.\n\nOur dapp is live on Sepolia for testing and you can check and test some of our features: https://app.namespace.tech/profile/list-and-manage \n\nCurrently in our Dapp users can:\n- Customize price:\n- - Set up base minting price\n- - Set up price based on subname length \n- - Set up number, character, emoji only price for subnames\n- Reserve subnames and disallow from minting\n- Reserve subnames and mint for special prices\n- Whitelist wallets to mint for free\n- Whitelist wallets that will be the only ones able to mint\n- Token-gated minting (for communities). Supports ERC20, 721, and 1155 standards. And ensures only people holding certain NFTs can mint subnames from listed ENS names. \n- Sell subnames through your own website or blog using our ENS Widget\n- Offer ENS Name registration services through our ENS Widget.\n-  Issue (sell or gift) subnames through Farcaster Frames.\n- Register ENS name or a subname\netc. 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": "On the financial front, our project tackles the common issue of errors in typing or copying lengthy 0x addresses, which can lead to the loss of funds. By adopting an ENS name or subname, users can sidestep this risk entirely, making transactions smoother and safer.\n\nEducationally, we are big believers in the power of self-sovereign and generative identities. These concepts empower users to control their own data and decide whom to share it with. Since every digital identity begins with a name, ENS becomes a pivotal educational tool in this context, helping people understand and navigate their presence in the digital world.\n\nRegarding the social impact - entirely moving away from 0x addresses and making .eth names/subnames a new industry standard and naming convention for wallets will significantly lower the barrier to entry for many people. This new standard makes it easier for newcomers to join and navigate the crypto space, paving the way for broader adoption and inclusivity.", "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": "Under the signed ToS with the ENS Foundation, we are obligated to publish everything we build under the MIT open-source 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": "Namespace is currently in an advanced development stage, fully operational for issuing and managing subnames on Ethereum. Now that we\u2019ve got our basic setup done, we're ready to make our platform even better. Our focus is on expanding our features and functionalities to enrich the subname management experience, delivering even greater value to our users.\n\n# Next Steps\n\n# Roadmap\n### Next steps for Q2 and Q3\n\n- **Infrastructure Expansion**: Develop and deploy infrastructure to support issuing (minting and storing) Subnames on Arbitrum, Optimism, and Base for more efficient and cheap management. \n- **EVM Gateway Enhancement**: Develop and deploy a modified version of the EVM gateway that acts as a bridge between L1 and L2s.\n- **Scalability**: Scaling up our infrastructure to support larger user bases.\n- **Farcaster Frames Integration**: Continue development on Farcaster Frames, enabling users to mint digital identities (subnames) from ENS names via a frame on Warpcast. \n- **Front-end integration**: Integrate our entire infrastructure into the frontend of our Dapp, making it straightforward for non-technical users to leverage our innovations. \n- **Dapp Redesign**: Currently working on an entirely new design for our Dapp which will make it even more user-friendly\n- **Partnerships**: We are actively seeking partnerships with major wallet providers, infra providers, wallet-as-a-sevice providers, games, communities, and individuals with ENS names who want to issue subnames, to ensure wide adoption.\n\nOverall continuous platform improvement based on user feedback. Our roadmap is designed to be flexible to adapt to new developments in the blockchain space and user demands. Our ultimate goal is to make Namespace a key player in the Web3 identity space, known for reliability, user-friendliness, and innovation.\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": "Receiving this grant would significantly extend our runway at Namespace, enabling us to potentially expand our team by hiring an additional full-time member. \n\nWe would allocate these funds towards further development of our dapp, incorporating new features to meet our users' needs more effectively. \n\nFurthermore, the funding would support our efforts to maintain open, responsive communication channels in Discord. This will allow us to assist ENS name owners with custom implementations and provide guidance on the best strategies for issuing subnames.\n\nAdditionally, we will build supporting developer documentation for web3 builders to use that will make using ENS subnames easier. ", "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": "We've been working full-time on Namespace since receiving the grant in January. Before that, we were working on this only nights and weekends. \n\nYou can see our Q1 Progress Report here: https://discuss.ens.domains/t/namespace-quarterly-reports/19057\n\nLoom Platform demo: https://www.loom.com/share/83996ab2dfd64756ab1d59654a3f9132?sid=4d78ee81-d188-4c9a-b39c-93fe07790e48\n\n", "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": "0xc9d476940e64684cbeed5b9c71f123bb114b69d908bce5d64f66a3503310750a", "title": "Namespace - ENS-based web3 identity platform", "logoImg": "bafkreidsxhnlilqjmaahm3veobtcngtulrru3mpmjt6zzrejejwwuyz4hq", "metaPtr": {"pointer": "bafkreiaw4tfwspz5eixvcgbgxz3ttgnvemkzp3upcgretzvvq2bbqmokam", "protocol": "undefined"}, "website": "https://namespace.tech/", "bannerImg": "bafkreievd3jqoyudhr5auex7s2uhd6t6nsj6xraq3iblwnqmditv3avble", "createdAt": 1713956280545, "userGithub": "", "credentials": {"twitter": {"type": ["VerifiableCredential"], "proof": {"jws": "eyJhbGciOiJFZERTQSIsImNyaXQiOlsiYjY0Il0sImI2NCI6ZmFsc2V9..MeHVJk9FUqfQactgdrybmItp5S132gzTupBYMq83jfJ1ilBmYV_WGkLETba7HcFjjmBmXygXlasHoYM-A_SGAw", "type": "Ed25519Signature2018", "created": "2024-04-24T10:51:53.691Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC#z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC"}, "issuer": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC", "@context": ["https://www.w3.org/2018/credentials/v1"], "issuanceDate": "2024-04-24T10:51:53.691Z", "expirationDate": "2024-07-23T10:51:53.691Z", "credentialSubject": {"id": "did:pkh:eip155:1:0x035eBd096AFa6b98372494C7f08f3402324117D3", "hash": "v0.0.0:h6jY959UC4AnwD6uQA94CaZMVVvtfxVV4nLLkbRxTWs=", "@context": [{"hash": "https://schema.org/Text", "provider": "https://schema.org/Text"}], "provider": "ClearTextTwitter#namespace_eth"}}}, "description": "# One-sentence summary\nNamespace is an ENS subname management platform and developer toolkit that aims to streamline ENS adoption, supercharge its utility, and grow its user base. \n\n# What do we do\nWe provide the most comprehensive suite of tools and features for ENS name owners to get the most out of their ENS names by issuing and managing subnames as digital identities. Whether they are communities, wallets, games, or individuals looking to onboard people to crypto, we provide a user-friendly platform that lets them do this easily with no technical skills required. \n\nFurthermore, a big part of our practice is centered around experimenting with new technologies and innovations in the space. Therefore, we build on different protocols and apps, leveraging innovation and trends in the space and finding innovative ways to allow ENS name owners to issue ENS-based web3 identities as subnames.\n\n# Ongoing stuff we're working on\n- We are building the entire infrastructure that would support issuing ENS Subnames on L2s such as Arbitrum, Optimism, and Base chain. Once ready, it would support adding other L2 chains fairly easily in the future. \n- Working on improving EVM Gateway.\n- Issuing Subnames through Farcaster Frames (launched last week with 2 partners and already 8k ENS Subnames issued)\n- Enriching our platform with new features based on the community's feedback\n- Integrating with infra providers (so far - QuickNode, Tatum, Web3js, etc.)\n- New Dapp design\n- And a lot, a lot more.\n\n\n# Team\nThe team behind Namespace: Cap (thecap.eth), Bran (branz.eth), and Arthy (artii.eth). Web3 natives! \n\nWe\u2019ve been working with ENS for almost 2 years now and are one of the 9 official ENS Service Providers that has received a grant from the ENS Foundation to continue building and improving Namespace and executing on our mission - to grow and streamline the adoption of ENS and build the most complete user-centric platform for easy ENS name and subname management.\n\n# Namespace links\nWebsite: https://namespace.tech/\nPlatform: https://app.namespace.tech/\nDocs: https://docs.namespace.tech/\n\n# Demo\nLoom demo: https://www.loom.com/share/83996ab2dfd64756ab1d59654a3f9132?sid=4d78ee81-d188-4c9a-b39c-93fe07790e48\n", "lastUpdated": 0, "projectGithub": "thenamespace", "projectTwitter": "namespace_eth"}, "recipient": "0x14Eaf911D7108fc434C79fC6ce99654Ac046299D"}}