{"signature": "0xda3526d1c3087026385914a24ffe16583daa9c6dd4962ebd170dd730fd390d6a18a5526baa41a59a01610332f7c6d93b7178f6d397e7d8da9129a63b201d3ec11c", "application": {"round": "0x1b48bb09930676d99dda36c1ad27ff0a5a5f3911", "answers": [{"type": "email", "hidden": true, "question": "Email Address", "questionId": 0, "encryptedAnswer": {"ciphertext": "4bAfw/XR0TagjsOe5WE2KzYC4U7GYnu0iyP0Ng6kQh7VsEb+1X/RnPHd5OlTgDls", "encryptedSymmetricKey": "23f312c4002e165a72cdb54854ff3a12ff542330e601ca2a671e5500e52c2495601cbb1e0986802769c4e507185f9d16279844c6183ebacf95f3026246cc7689363c97f32641deee295c6be1f7a78bf25d72e743f401fce2ffabf6877f67bf8fc8b38e82ff6bc579c613489ad799c0ce5c4f61ac07a07b0be2890391c158cd7700000000000000208a82b4a137417da0081896ea3725aaebf22315de2e08cc8059db6081a9d9e5ee35d40dc679a07356640e014b43b3eeaa"}}, {"type": "short-answer", "hidden": true, "question": "Telegram Handle We Can Use To Contact You(you can answer N/A)", "questionId": 1, "encryptedAnswer": {"ciphertext": "GmLeJ8Y53y4LhGui4evSwtAKS+ZSu6QnsIrAYdQD+ag=", "encryptedSymmetricKey": "2eada771e348d92f71dc60e9b0adeca9ce9bfec5c778d7cd1918fe904511a2f9ac6f240ac516b4371290cd97ba731a055f3dbc8821f6732f46df90b35a3fa605a7a3903acf665c894b2b050af1179beee5719d4948b7f567690f638728d00ba030030ce3acdb60b6ff1fadca9d8402868d0121ef56d821ed1623c56e65f8dce40000000000000020ef3efb6c02b610ee1966d15b839cb676049f967f43c4fe639f24b1db1b27517d077ce297ce6663da802c74665ab36899"}}, {"type": "link", "answer": "https://github.com/DappReader/DappReader-v2", "hidden": false, "question": "Project GitHub Repo (Not Team Page): ", "questionId": 2}, {"type": "number", "answer": "2", "hidden": false, "question": "Total Team Size", "questionId": 3}, {"type": "paragraph", "answer": "lidamao-0xb0eE1755460DdDb01F73104dF2E61a89b0464885\nTiyo-0xbbA51F0b09d5852eFfa609E9223ba7F5d7407945", "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/DappReader", "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", "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’t 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": "The impact and effectiveness of our project are primarily observable through statistical data provided by our cloud service provider, Cloudflare. As a project focused on offering a suite of developer tools in the niche and vertical segment of Web3, we are committed to providing high-quality and practical toolsets to support the growth and development of the developer community.\n\nAccording to Cloudflare's statistics over the past seven days, our tools have attracted 674 unique visitors and processed a total of 20,350 requests. These metrics reflect our project's acceptance and active usage within the Web3 developer community. The number of unique visitors provides a window into our ability to attract new users, while the total number of requests showcases the existing users' reliance on and active engagement with our tools.", "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": "0", "hidden": false, "question": "Total Prior Funding 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": "12", "hidden": false, "question": "How old (in Months) is the project?  ", "questionId": 12}, {"type": "checkbox", "answer": ["Asia", "Somewhere in the Metaverse", "North America"], "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": "multiple-choice", "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": "\ndappreader.com is a tool specifically designed to help developers quickly debug smart contracts, greatly facilitating the tagging and joint debugging between front-end and smart contract developers. Its role in the domain of smart contract development is akin to Postman, providing an intuitive and powerful interface that allows developers to send, receive, and review smart contract interactions.\n\nWithin the Web3 development, framework, or testing tool ecosystem, dappreader.com offers a crucial platform. It enables developers to gain a deeper understanding of the workings of smart contracts, enhancing development efficiency and fostering effective communication and collaboration among teams, especially during the integration phase of front-end and smart contracts.\n\nBy simplifying the process of testing and debugging smart contracts, dappreader.com provides an accessible environment for developers, accelerating the development cycle of decentralized applications (DApps) and helping teams deliver projects on schedule.", "hidden": false, "question": "Please describe the developer tool or library you're working on. How does it fit into the development environments, frameworks, or testing tools landscape for Web3? ", "questionId": 16}, {"type": "paragraph", "answer": "\nWe measure the adoption of our tool or library through various methods to accurately reflect its usage within the developer community. Here are some key metrics we use:\n\nUsage: We track website traffic, including unique visitor counts, page views, and the number of times specific features are used, through Cloudflare's analytics. This data helps us understand which features are most popular and how users engage with our tool or library.\n\nGitHub Metrics: We closely monitor related metrics on GitHub, such as the number of stars, forks, issues opened and resolved, and the activity around pull requests. These metrics offer valuable insights into the developers' interest in and usage of our tool or library, as well as reflect the community's support and contributions to the project.\n\nUser Feedback: Gathering direct feedback from users is another critical aspect of assessing the adoption of our tool or library. We collect users' opinions and suggestions through community forums, emails, and direct surveys. This feedback helps us continuously optimize our product to better meet users' needs.\n\nThese comprehensive metrics allow us to fully understand the performance of our tool or library in the market and how it is adopted and utilized by the developer community. This data is crucial for guiding our product development direction and making strategic decisions.", "hidden": false, "question": "Please provide details on how you measure the adoption of your tool and/or library. Do you have metrics on usage, downloads, and installs?", "questionId": 17}, {"type": "paragraph", "answer": "\ndappreader significantly enhances the collaboration efficiency between contract developers and non-contract developers through its innovative team feature. By simplifying the testing and debugging process of smart contracts in a manner similar to Postman, it not only accelerates the development process of smart contracts but also promotes internal communication and collaboration within teams. In terms of security, dappreader provides two key features:\n\nInternal Open Source: During the development phase, dappreader allows the code to be open source within the team only. This strategy effectively prevents the early leakage of the code, protecting the project's security and uniqueness. Through this approach, team members can freely share, review, and optimize the code without worrying about external security risks.\n\nAI-based Automatic Code Auditing: dappreader also introduces an AI-based automatic code auditing feature, enabling developers to quickly identify and correct some fundamental coding errors. This intelligent auditing tool greatly improves the quality and security of the code, reducing the security risks that may arise from common vulnerabilities or improper coding.\n\nBy providing convenient team collaboration features and enhanced security measures, dappreader becomes both an efficient and secure tool for smart contract development. It not only makes the development of smart contracts more convenient but also ensures project security through advanced technology, making it an indispensable tool for developing decentralized applications.\n", "hidden": false, "question": "How does your project address the need for secure and efficient smart contract development? If applicable, detail the library's features or capabilities that cater to this need.", "questionId": 18}, {"type": "paragraph", "answer": "\n\nIn the process of smart contract development, we identified several major bottlenecks in efficiency, particularly in the communication and exchange of smart contract information among contract developers, front-end developers, and testers. Due to frequent changes in function names, functionalities, and parameters in smart contracts, team members often spend a significant amount of time updating and synchronizing information. Additionally, development teams typically do not wish to open source their code during the testing phase, meaning information can only be shared via text documents, further complicating communication. Testers often need to write a large number of one-time test files for testing purposes, which is not only inefficient but also a waste of time.\n\nTo address these issues, we implemented the following solutions with dappreader:\n\nUnified Interaction Interface: dappreader provides a unified interaction interface for contract developers, front-end developers, and testers, allowing for real-time synchronization of information such as smart contract function names, functionalities, and parameters. This significantly reduces the communication costs and time wasted due to inconsistent information.\n\nSecure Internal Sharing Mechanism: Our tool allows teams to securely share test versions of smart contracts internally without making the code public, ensuring the security of information during the testing phase. This avoids the cumbersome process of document exchange while ensuring the immediate update and accuracy of information.\n\nAutomated Test Script Generation: dappreader also supports the automatic generation of test scripts, reducing the need for testers to write a large number of one-time test files. This not only improves the efficiency of testing but also ensures the comprehensiveness and accuracy of test coverage.", "hidden": false, "question": "Can you demonstrate how your tool or library significantly reduces barriers to development or enhances project efficiency in the OSS or Web3 ecosystems? Provide examples or case studies of your tool in action.", "questionId": 19}, {"type": "paragraph", "hidden": false, "question": "Anything else you'd like to share about your project, previous work, or other project affiliations? Is there anything you'd like to add that may help determine project eligibility?", "questionId": 20}, {"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": 21}, {"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": 22}], "project": {"id": "0x0fd89d63362aeff73772911183115346ad8956f7a0b1e2783adb4004dbb1cf17", "title": "DappReader", "logoImg": "bafkreih7uet3ujntfuzfvc6e4cwlmwan5cakixsrw7wqc6awkruomh4bba", "metaPtr": {"pointer": "bafkreiccuo2ixsw4rcib52hk7xny7zolt5qzwtqcdwwccxbjfyz5ythj44", "protocol": "undefined"}, "website": "https://DappReader.com", "bannerImg": "bafkreifxza5qzen2glmwhk5zxu7p5fggqwyckpes34pjebn7xak5nprhya", "createdAt": 1682332236717, "userGithub": "LidamaoHub", "credentials": {"github": {"type": ["VerifiableCredential"], "proof": {"jws": "eyJhbGciOiJFZERTQSIsImNyaXQiOlsiYjY0Il0sImI2NCI6ZmFsc2V9..tANvR0ZmLmBYq1a333KwbJRM0fB8Z58zEbWtgSujCNTj0n4InN79s-xdb-go9GBHKkh5NT9v6-dshX21F482DQ", "type": "Ed25519Signature2018", "created": "2023-04-24T10:30:21.211Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC#z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC"}, "issuer": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC", "@context": ["https://www.w3.org/2018/credentials/v1"], "issuanceDate": "2023-04-24T10:30:21.211Z", "expirationDate": "2023-07-23T10:30:21.211Z", "credentialSubject": {"id": "did:pkh:eip155:1:0xb0eE1755460DdDb01F73104dF2E61a89b0464885", "hash": "v0.0.0:9+n2EXbq1UN2LTpJpMOmNLXnjZNBLldDIn+ZsN6Zzv4=", "@context": [{"hash": "https://schema.org/Text", "provider": "https://schema.org/Text"}], "provider": "ClearTextGithubOrg#DappReader#6832146"}}, "twitter": {"type": ["VerifiableCredential"], "proof": {"jws": "eyJhbGciOiJFZERTQSIsImNyaXQiOlsiYjY0Il0sImI2NCI6ZmFsc2V9..TEdaBSIJx3J6SevKVB06h-HpLPmN_zAKYGhGZ9TtBKxlYwh8ZMXa56CkQAWLcRvoMoEMHi_sR_t1bDhuOeLuDA", "type": "Ed25519Signature2018", "created": "2023-04-24T10:29:42.910Z", "proofPurpose": "assertionMethod", "verificationMethod": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC#z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC"}, "issuer": "did:key:z6MkghvGHLobLEdj1bgRLhS4LPGJAvbMA1tn2zcRyqmYU5LC", "@context": ["https://www.w3.org/2018/credentials/v1"], "issuanceDate": "2023-04-24T10:29:42.910Z", "expirationDate": "2023-07-23T10:29:42.910Z", "credentialSubject": {"id": "did:pkh:eip155:1:0xb0eE1755460DdDb01F73104dF2E61a89b0464885", "hash": "v0.0.0:w4yANfEa3Nw6iQh4w2M7HwIMVr+piB6tATX+Lxw5QdE=", "@context": [{"hash": "https://schema.org/Text", "provider": "https://schema.org/Text"}], "provider": "ClearTextTwitter#DappReader"}}}, "description": "# DappReader\n\n\n\n![cover](https://github.com/DappReader/DappReader-v2/raw/main/img/intro.png)\n\n### **DappReader是一款令我们自豪的产品,一款全面面向EVM生态开发者服务的免费工具**\n\nDappReader旨在为开发者提供已发布的多链合约的管理和快速前端-合约调试。这款工具将帮助开发者更加高效地开发、测试和部署合约项目，提升项目的开发质量和效率。\n\n> 你可以简单理解为对标web2时代的的 **Postman** !\n\n### 你是否也有相同烦恼:\n\n1. 使用Remix和Etherscan.io等工具处理已有合约或调试新合约非常不友好，并且需要频繁地更新和验证代码。\n2. 写过的合约很久后忘记在哪里,需要翻交互记录才能找到\n\n3. 与团队成员或其他前端工程师进行远程协作时也很繁琐。\n\n4. 另外，让非开发人员使用智能合约需要写复杂的UI并部署到中心化服务器上。\n\n### DappReader的主要功能:\n1. 多种方式方便添加与管理所有EVM链智能合约\n2. 快速检索与管理已发布的合约\n3. 无代码快速生成智能合约操作界面\n4. 对智能合约整体以及每一个函数单独进行注释\n5. 与开发者或非开发者快速分享开发中的智能合约(包含注释),方便合约工程师与前端工程师联调\n6. 提供完全免费的团队分享功能,非常适合小团队使用\n7. 提供一系列类型转换工具,减少开发者工作量\n\n\n\n### DappReader未来功能:\n\n1. 加入更多AI功能\n2. 基于多个智能合约流程执行功能\n3. 基于外部变化自动执行合约的Trigger功能\n4. 用户无代码生成简单前端页面并分享功能\n5. 集成Remix完成一站式开发测试分享功能\n6. 深度结合web2与web3,完成**web3os**\n\n### DappReader功能介绍:\n![invite](https://github.com/DappReader/DappReader-v2/raw/main/img/invite.png)\n\n快速与团队成员分享智能合约\n\n![file](https://github.com/DappReader/DappReader-v2/raw/main/img/file.png)\n\n快速管理个人与公司的多个链上智能合约\n\n![file](https://github.com/DappReader/DappReader-v2/raw/main/img/edit.png)\n\n轻松标注智能合约函数,与队友共享\n\n![file](https://github.com/DappReader/DappReader-v2/raw/main/img/transaction.png)\n\n更方便,更智能的输入纠错,自动数据decimal转换\n\n\n### 加入我们的中文社区\n![group](https://github.com/DappReader/DappReader-v2/raw/main/img/group.png)\n\n### Do you have the same frustrations as well:\n\n1. It is very unfriendly to use tools like Remix and Etherscan.io to handle existing contracts or debug new contracts, and the code needs to be updated and verified frequently.\n2. After a long time, you forget where you wrote the contract and need to search through communication records to find it.\n3. It is also cumbersome to collaborate with team members or other front-end engineers remotely.\n4. Additionally, making non-developers use smart contracts requires writing complex UI and deploying them to centralized servers.\n\n### Main Features of DappReader:\n\n1. Conveniently add and manage all EVM chain smart contracts in various ways.\n2. Quickly search and manage published contracts.\n3. Quickly generate smart contract operation interfaces without code.\n4. Add comments to the entire smart contract or each individual function.\n5. Quickly share developing smart contracts (with comments) with developers or non-developers, making it easy for contract engineers to collaborate with front-end engineers.\n6. Provides completely free team-sharing function that is ideal for small teams.\n7. Provides a series of type conversion tools to reduce the workload for developers.\n\nDappReader Roadmap:\n\n1. Adding more AI functionality.\n2. Functionality for executing multiple smart contract processes.\n3. Trigger functionality for automatically executing contracts based on external changes.\n4.  Functionality for users to generate simple front-end pages without code and share them.\n5. Integration with Remix to provide one-stop development, testing, and sharing features.\n6. Deep integration of web2 and web3 to complete web3os.\n\n", "lastUpdated": 0, "projectGithub": "DappReader", "projectTwitter": "DappReader"}, "recipient": "0xb0eE1755460DdDb01F73104dF2E61a89b0464885"}}