metadata: {"signature": "0xdb306cd44329a112ca1a2c5e4a4f7ea9a436e92e58a7cdbf376a80ddc3a4d2970a18f5bf2028e3ef6d14fbabf41e50f0fed4b5b47d481ca8ab27851830b0bc2f1b", "application": {"round": "0x1b48bb09930676d99dda36c1ad27ff0a5a5f3911", "answers": [{"type": "email", "hidden": true, "question": "Email Address", "questionId": 0, "encryptedAnswer": {"ciphertext": "WQH5v48lLDkIyoXLV7b1rm9Kw135AeVlefB83YI8lJA=", "encryptedSymmetricKey": "b27cd697ee2e852c132a6a3e655a41f9358f6dabd6e2776302a59ffe809f4682182e8482eec8101b1b6f995b52e2a70c92a73531e2a2b465f00c8bab6922e5ebc7f4f82bb283728134856b1961e5015e21033b26a49597830c13545f30a087b614bd48ddb81e7fc10e89b0bc6d67e4abd576310fd242d1efdc555065cc5d20550000000000000020cd263742278bb9eb34b5cea01ec59baf1bfc74cf29d814678422ca4e053069d336a5041a73679deeeb152bb12c7444b1"}}, {"type": "short-answer", "hidden": true, "question": "Telegram Handle We Can Use To Contact You(you can answer N/A)", "questionId": 1, "encryptedAnswer": {"ciphertext": "VrFrUTaiL1BwDBCSFqNg+WsGdMts5gDG+tv8uZH/eSY=", "encryptedSymmetricKey": "6d569401af5b5175476918899e0408663b8901feca19e4c75501a9bbc3f6fb96b92bdb2b52b3b706f0ce33161b1fd10e33fb9c28e4473393f289f6c01dfd9e9c9916ed740c5e1a386a0b9aba8cff933bba13507e2e54c7000d67210c5366eb95bb5b3f08135fb11c0e68e06b2222faf3ea0afeef1f7c2ef86f30972c8730f8f70000000000000020d48b0dbdcf37d3ac1863bd4f2e05b1d7062bf213571575b0b2d9d1f1d8d0a1ec39325f22c38070e58e8491d7b2663b8a"}}, {"type": "link", "answer": "https://github.com/bonadocs/protocol-registry", "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": "We have hands-on experience building globally renowned web3 developer products such as consensys.net (metamask and infura). We\u2019ve also contributed to major protocols in web3 such as the Origin Protocol and Ethers.\n\nAhmad Alfawwaz Timehin (Blockchain / Smart Contracts Developer - Contributor @ Origin Protocol, Ethers, The Graph  & Lead Reverse Engineer, Mono) - (https://www.linkedin.com/in/staa99) - Co-founder  & CTO - staa99.eth\nDavid Atanda (Ex- UX Engineer, Consensys) (https://www.linkedin.com/in/david-atanda/) - Co-founder & CEO. - astrodavid.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/thisdavidboy\nhttps://twitter.com/staa99", "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\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": "The impact of our project boils down to how many protocols and networks are using Bonadocs. \n\nProgress\n\n- ConsenSys Fellowship Maiden Cohort  (https://consensys.io/blog/introducing-the-first-cohort-of-the-consensys-fellowship-program-for-web3)\n- $68k grants/revenue. This includes receiving an Arbitrum grant to build a protocol registry for Arbitrum and integrate Bonadocs\u2019 widgets into arbitrum protocols. Also, adding interactivity to Compound Finance\u2019s documentation - https://questbook.app/dashboard/?proposalId=0x5d3&role=community&chainId=10&isRenderingProposalBody=true&grantId=0x3b16764826f0baa77226327c7c0d7d53f8541913\n\nIntegrations: We're actively integrating with Compound, Axelar, Paycrest, Superfluid, Hedgey finance, etc.", "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": "$68,000", "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": "5", "hidden": false, "question": "How old (in Months) is the project?  ", "questionId": 12}, {"type": "checkbox", "answer": ["Asia"], "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": "Bonadocs is building the future of secure smart contract development and distribution. It's a collaborative tool for documentation, organization, facilitating contract interactions for simple & complex workflows. This also includes an AI co-pilot for crafting gas-efficient and secure contract flows.", "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": "The adoption of our project boils down to how many protocols and networks are using Bonadocs. \n\nProgress\n\n- ConsenSys Fellowship Maiden Cohort  (https://consensys.io/blog/introducing-the-first-cohort-of-the-consensys-fellowship-program-for-web3)\n- $68k grants/revenue. This includes receiving an Arbitrum grant to build a protocol registry for Arbitrum and integrate Bonadocs\u2019 widgets into arbitrum protocols. Also, adding interactivity to Compound Finance\u2019s documentation - https://questbook.app/dashboard/?proposalId=0x5d3&role=community&chainId=10&isRenderingProposalBody=true&grantId=0x3b16764826f0baa77226327c7c0d7d53f8541913\n\nIntegrations: We're actively integrating with Compound, Axelar, Paycrest, Superfluid, Hedgey finance, etc.", "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": "## Problem\n\nTwo things that have slowed down the global adoption of web3 are user experience and developer experience issues. There have been significant strides in the former with the emergence of UX products like biconomy, web3auth, etc . Bonadocs is taking the lead with the latter by giving builders the best experience possible to develop and distribute new protocols/dapps and integrate effectively with existing protocols.\n\nThe major problems builders\u2019 face today includes: \n\n- Collaboration between internal web3 engineering teams is fragmented.\n- Smart contract documentation and interactions is complex.\n- Integrations for simple and complex workflows is a nightmare.\n- Testing for smart contracts is still mostly manual.\n- Smart contract security and hacks is a big issue in web3 leading to loss of funds.\n- Gas fees is still an obstacle to onboarding the next billion users.\n\n**Details**: Collaborating between teams on smart contract integrations is currently a time-consuming affair. This comes down to two difficult tasks:\n\n- Documentation\n- Integration\n\nDocumenting smart contracts is hard. Most smart contracts have complex workflows. Multiple smart contract method calls and transactions are required to complete certain complex actions. For example, executing a Swap action on Uniswap involves at least two calls for most tokens: approve tokens (approve), execute swap (transferFrom). Each workflow needs to be properly documented.\n\nIntegration is also a nightmare because few contracts are ever documented well\nenough. However, that's not the only reason. Even when the contract is adequately\ndocumented, testing workflows to observe the behavior in different scenarios is a necessary part of integration. For both solidity and dapp developers.\n\nOne more thing to note is that, **Contract security** is exclusively assessed from the point of audits that happen post-deployment; which is very expensive. This means devs have to pay for this high  audit cost before determining if their project actually solves the user\u2019s problems or even figure out their business model. \n\nFinally, as we scale, we need to further reduce the cost of gas required to interact with our dapps. L2s have allowed us build on chains that have low gas fees, but that\u2019s not enough. We need to ensure the contract itself requires a negligible amount of gas fee to easily onboard new users.\n\n## Solution\n\nBonadocs is building the future of secure smart contract development and distribution. It's a collaborative tool for documentation, organization, facilitating contract interactions for simple & complex workflows. This also includes an AI co-pilot for crafting gas-efficient and secure contract flows.\n\n### Documentation\n\n**Docgen:** This allows developers to automatically generate a beautiful and interactive documentation website for your project directly from your development environment; using a hardhat plugin.\n\nDemo: https://www.loom.com/share/672398e483364eaa87303529736de709\n\n### Integration & Distribution\n\n**Bonadocs Widget:** For context, when reading Lido\u2019s documentation, you have the explanation of the protocol contracts, but in order to interact with the verified contracts, you\u2019d have to go to etherscan or simulate on hardhat. The goal of the widget is to enable developers to interact with the contract methods as a widget directly within the docs.\n\nThis allows developers to seamlessly interact with the protocol\u2019s contracts without switching to other external tools. The idea is that the widget will replace the function code sections where the function names are usually written. By using the widget rather than just text function names and signatures, developers can actually interact with those functions directly from the page. In some of the guides, there's usually a more workflow-like usage that requires more than one contract method to complete the action. Adding the widget to the page would help developers understand the docs better by letting them simulate interactions with the contracts and see the results and emitted logs.\n\nDemo: https://www.loom.com/share/9affc4deecde438cb108efb4bd188c1c\n\n![Screenshot 2024-01-27 at 08.38.48.png](https://prod-files-secure.s3.us-west-2.amazonaws.com/2b0bda16-60a5-4f0b-b45a-1c6f815280ee/a87c15f7-3dca-4f78-a5db-f63433389c52/Screenshot_2024-01-27_at_08.38.48.png)\n\n**Bonadocs Editor (For Teams):** Create projects, aggregate your contracts, enable internal/external teams to document, collaborate, interact with contracts, automate testing, and simulate complex workflows.\n\nFeatures:\n\n- Project creation directly from the command line.\n- Project collaboration\n- Protocol Playground\n- Contract interaction (mainnet/simulation)\n- Actions\u2019 code editor - This allows users to interact with their smart contracts using a Javascript environment; just like they\u2019re on the frontend of the application.\n- Inbuilt Docgen/Widget\n- Event logs\n- Automatically creating NPM libraries for smart contracts in a project. This makes it absolutely easy for any frontend/dapp developer to call the contract methods/actions because it\u2019ll be abstracted into library methods.\n    \n    ![Screenshot 2024-01-27 at 08.46.03.png](https://prod-files-secure.s3.us-west-2.amazonaws.com/2b0bda16-60a5-4f0b-b45a-1c6f815280ee/414fa998-b5df-485b-8063-7b3659dbc36a/Screenshot_2024-01-27_at_08.46.03.png)\n    \n\n**Bonadocs Protocol Registry:** The protocol registry allows networks share a list of protocols existing on their network. Each protocol links to an editor that allows devs interact with their contract methods and dapp actions.\n\n![Screenshot 2024-01-27 at 08.40.31.png](https://prod-files-secure.s3.us-west-2.amazonaws.com/2b0bda16-60a5-4f0b-b45a-1c6f815280ee/639bf9f0-fead-49c4-b81a-f20bfe848146/Screenshot_2024-01-27_at_08.40.31.png)\n\nAlso, another use-case we are looking to explore is to help protocols sell or distribute their protocols to other protocols and dApps using automatically generated interactive demos and UI for their smart contracts. This is very important today as more protocols/dapps begin to build on foundational protocols like Uniswap, Lido, Farcaster, etc. This creates a more intuitive way to onboard developers by showcasing real-life usage outside the documentation. This can be used by Sales folks for outreaches or even PMs for internal alignment across teams. \n\nWe believe this can have a major ripple effect in terms of the growth of consumer dapps and collaborations with web2 products (inclu. attestation in AI products). \n\nIt can expand the web3 market through protocol startups by helping to productize their smart contracts to third-party startups (web3/web2), similar to web2 API startups like Message bird or Twilio.\n\n### Security\n\nTo expand, the security tool is linked to your vscode (similar to github copilot), so once you write code, it alerts you of security vulnerabilities in your smart contracts.\n\nSo it's more of a workflow thing rather than waiting till the end of your entire code deployment for a security audit.\n\nIt basically leverages AI by learning from many security audit reports and is able to detect such patterns in your smart contract code.\n\n### Development & Scalability\n\nSmart Contract Automated Testing: Automatically generate tests from contract code. It improves productivity by generating tests. Technically, if the generated tests do not align with your intended logic, you can be sure that your written logic is faulty.\nGas optimization tool for contracts: It\u2019s a feature leveraging AI that\u2019s linked to vscode and allows engineers to perform automated gas audits on their smart contracts and suggests ways to cut down gas costs.", "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": "## Solution\n\nBonadocs is building the future of secure smart contract development and distribution. It's a collaborative tool for documentation, organization, facilitating contract interactions for simple & complex workflows. This also includes an AI co-pilot for crafting gas-efficient and secure contract flows.\n\n### Documentation\n\n**Docgen:** This allows developers to automatically generate a beautiful and interactive documentation website for your project directly from your development environment; using a hardhat plugin.\n\nDemo: https://www.loom.com/share/672398e483364eaa87303529736de709\n\n### Integration & Distribution\n\n**Bonadocs Widget:** For context, when reading Lido\u2019s documentation, you have the explanation of the protocol contracts, but in order to interact with the verified contracts, you\u2019d have to go to etherscan or simulate on hardhat. The goal of the widget is to enable developers to interact with the contract methods as a widget directly within the docs.\n\nThis allows developers to seamlessly interact with the protocol\u2019s contracts without switching to other external tools. The idea is that the widget will replace the function code sections where the function names are usually written. By using the widget rather than just text function names and signatures, developers can actually interact with those functions directly from the page. In some of the guides, there's usually a more workflow-like usage that requires more than one contract method to complete the action. Adding the widget to the page would help developers understand the docs better by letting them simulate interactions with the contracts and see the results and emitted logs.\n\nDemo: https://www.loom.com/share/9affc4deecde438cb108efb4bd188c1c\n\n![Screenshot 2024-01-27 at 08.38.48.png](https://prod-files-secure.s3.us-west-2.amazonaws.com/2b0bda16-60a5-4f0b-b45a-1c6f815280ee/a87c15f7-3dca-4f78-a5db-f63433389c52/Screenshot_2024-01-27_at_08.38.48.png)\n\n**Bonadocs Editor (For Teams):** Create projects, aggregate your contracts, enable internal/external teams to document, collaborate, interact with contracts, automate testing, and simulate complex workflows.\n\nFeatures:\n\n- Project creation directly from the command line.\n- Project collaboration\n- Protocol Playground\n- Contract interaction (mainnet/simulation)\n- Actions\u2019 code editor - This allows users to interact with their smart contracts using a Javascript environment; just like they\u2019re on the frontend of the application.\n- Inbuilt Docgen/Widget\n- Event logs\n- Automatically creating NPM libraries for smart contracts in a project. This makes it absolutely easy for any frontend/dapp developer to call the contract methods/actions because it\u2019ll be abstracted into library methods.\n    \n    ![Screenshot 2024-01-27 at 08.46.03.png](https://prod-files-secure.s3.us-west-2.amazonaws.com/2b0bda16-60a5-4f0b-b45a-1c6f815280ee/414fa998-b5df-485b-8063-7b3659dbc36a/Screenshot_2024-01-27_at_08.46.03.png)\n    \n\n**Bonadocs Protocol Registry:** The protocol registry allows networks share a list of protocols existing on their network. Each protocol links to an editor that allows devs interact with their contract methods and dapp actions.\n\n![Screenshot 2024-01-27 at 08.40.31.png](https://prod-files-secure.s3.us-west-2.amazonaws.com/2b0bda16-60a5-4f0b-b45a-1c6f815280ee/639bf9f0-fead-49c4-b81a-f20bfe848146/Screenshot_2024-01-27_at_08.40.31.png)\n\nAlso, another use-case we are looking to explore is to help protocols sell or distribute their protocols to other protocols and dApps using automatically generated interactive demos and UI for their smart contracts. This is very important today as more protocols/dapps begin to build on foundational protocols like Uniswap, Lido, Farcaster, etc. This creates a more intuitive way to onboard developers by showcasing real-life usage outside the documentation. This can be used by Sales folks for outreaches or even PMs for internal alignment across teams. \n\nWe believe this can have a major ripple effect in terms of the growth of consumer dapps and collaborations with web2 products (inclu. attestation in AI products). \n\nIt can expand the web3 market through protocol startups by helping to productize their smart contracts to third-party startups (web3/web2), similar to web2 API startups like Message bird or Twilio.\n\n### Security\n\nTo expand, the security tool is linked to your vscode (similar to github copilot), so once you write code, it alerts you of security vulnerabilities in your smart contracts.\n\nSo it's more of a workflow thing rather than waiting till the end of your entire code deployment for a security audit.\n\nIt basically leverages AI by learning from many security audit reports and is able to detect such patterns in your smart contract code.\n\n### Development & Scalability\n\nSmart Contract Automated Testing: Automatically generate tests from contract code. It improves productivity by generating tests. Technically, if the generated tests do not align with your intended logic, you can be sure that your written logic is faulty.\nGas optimization tool for contracts: It\u2019s a feature leveraging AI that\u2019s linked to vscode and allows engineers to perform automated gas audits on their smart contracts and suggests ways to cut down gas costs.", "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": "0xda9602c16090577afd33a6af76b18d4c711de8ee7d8d7081b6215523351d634e", "title": "Bonadocs", "logoImg": "bafkreib3bmzkcqzflnk6v4o4ubzmnzlqshksgvabl7ibqqib4ku2ryjee4", "metaPtr": {"pointer": "bafkreiewigvk56qq3vkauqkkvglxuspsxfp722razzlhjp4j25dxdgaxle", "protocol": "undefined"}, "website": "https://bonadocs.com", "bannerImg": "bafkreias7htfnfaeen6w6kqkaq5p2t2dkk5dgkn2d4wl7x5owo5hxlg6zi", "createdAt": 1707896202759, "userGithub": "atanda1", "credentials": {}, "description": "Bonadocs is building the future of secure smart contract development and distribution.\n\n", "lastUpdated": 0, "projectGithub": "bonadocs", "projectTwitter": "bonadocs"}, "recipient": "0x9d55D24105cd246115705A58CF92a5161A90B1fF"}}