├── .github └── pull_request_template.md ├── .gitignore ├── Applications ├── IoT-Data NFT Marketplace.md └── infinifty.md ├── CODE_OF_CONDUCT.md ├── LICENSE ├── README.md ├── applications ├── AmpleMintbase.md ├── DAOsign.md ├── MintBOS.md ├── MintBaseStudio-Metasky.md ├── Monad-Application.md ├── NearFT.md ├── PWX.md ├── PWXchange.md ├── QSTN-Mintbase-integration.md ├── RentVerse.md ├── Roketo-Mintbase-Integration.md ├── SLiC-Images.md ├── UML.jpg ├── WalliD verification SDK Grant Proposal.md ├── WalliD-MPC-Infra ├── allies-marketplace.md ├── application-gorilla-shops-automat.md ├── application_template.md ├── cootoo.md ├── deepskills.md ├── iindy_fka-twigs_sothebys ├── lightofEarendil.md ├── metronomo.md ├── mintbase-analytics-and-visulization .md ├── namesky.md ├── nano-store.md ├── playable-nft-marketplace.md ├── puzzletask_license_nft.md ├── the_everything_project.md ├── zettablock.md └── zkoracle-framework.md ├── docs ├── T&Cs.md ├── accepted_grant_applications.md ├── announcement-guidelines.md ├── ecosystem.md ├── faq.md ├── grant_guidelines_per_category.md └── milestone-deliverables-guidelines.md ├── maintenance └── maintenance-template.md ├── rfps ├── README.md └── applications │ └── mapz.md ├── src ├── Grants2-template-1600x900.png ├── badge_black.svg ├── like.png ├── map.png ├── medium.png ├── reddit.png ├── rfp-header.png ├── twitter.png ├── web.png └── youtube-play.png └── submissions ├── AmpleMintbase_milestone1_2024_09_27.md └── delivery_guidelines.md /.github/pull_request_template.md: -------------------------------------------------------------------------------- 1 | ### Project Abstract 2 | 3 | > Please provide a brief description of your project here summarising key points (1-2 paragraphs). 4 | > 5 | > If your application is a follow-up to a previous grant, please mention which one in the first line of the abstract and include a link to previous pull requests if applicable. 6 | 7 | ### For which grant [level](https://github.com/Mintbase/Grants-Program#level_slider-levels) are you applying? 8 | - [ ] **Level 1**: Up to $10,000, 2 approvals 9 | - [ ] **Level 2**: Up to $50,000, 3 approvals and one pitch to Mintbase Council 10 | - [ ] **Level 3**: Unlimited, 5 approvals and mutliple pitches to Mintbase Council 11 | 12 | ### Application Checklist 13 | 14 | - [x] The [application template](https://github.com/Mintbase/Grants-Program/blob/master/applications/application-template.md) has been copied, renamed ( `project_name.md`) and updated. 15 | - [ ] NEAR address for the payment of the milestones is provided inside the application. 16 | - [ ] I have read and acknowledged the [terms and conditions](https://github.com/Mintbase/Grants-Program/blob/master/docs/T&Cs.md). 17 | - [ ] The software delivered for this grant will be released under an open-source license specified in the application. 18 | - [ ] The initial PR contains only one commit (squash and force-push if needed). 19 | - [ ] The grant will only be announced once the first milestone [has been accepted](https://github.com/w3f/Grant-Milestone-Delivery#process). 20 | 21 | ### How Did You Hear About our grants program? 22 | 23 | - [ ] Mintbase Website 24 | - [ ] Mintbase Community (Twitter, Discord, Telegram etc.) 25 | - [ ] Hackathon 26 | - [ ] Personal Recommendation 27 | - [ ] Investor/VC 28 | - [ ] Online Search 29 | - [ ] Other: _______ 30 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | 2 | # Created by https://www.toptal.com/developers/gitignore/api/macos,windows 3 | # Edit at https://www.toptal.com/developers/gitignore?templates=macos,windows 4 | 5 | ### macOS ### 6 | # General 7 | .DS_Store 8 | .AppleDouble 9 | .LSOverride 10 | 11 | # Icon must end with two \r 12 | Icon 13 | 14 | 15 | # Thumbnails 16 | ._* 17 | 18 | # Files that might appear in the root of a volume 19 | .DocumentRevisions-V100 20 | .fseventsd 21 | .Spotlight-V100 22 | .TemporaryItems 23 | .Trashes 24 | .VolumeIcon.icns 25 | .com.apple.timemachine.donotpresent 26 | 27 | # Directories potentially created on remote AFP share 28 | .AppleDB 29 | .AppleDesktop 30 | Network Trash Folder 31 | Temporary Items 32 | .apdisk 33 | 34 | ### Windows ### 35 | # Windows thumbnail cache files 36 | Thumbs.db 37 | Thumbs.db:encryptable 38 | ehthumbs.db 39 | ehthumbs_vista.db 40 | 41 | # Dump file 42 | *.stackdump 43 | 44 | # Folder config file 45 | [Dd]esktop.ini 46 | 47 | # Recycle Bin used on file shares 48 | $RECYCLE.BIN/ 49 | 50 | # Windows Installer files 51 | *.cab 52 | *.msi 53 | *.msix 54 | *.msm 55 | *.msp 56 | 57 | # Windows shortcuts 58 | *.lnk 59 | 60 | # End of https://www.toptal.com/developers/gitignore/api/macos,windows 61 | 62 | # IDE settings 63 | .vscode 64 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Contributor Covenant Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | In the interest of fostering an open and welcoming environment, we as 6 | contributors and maintainers pledge to making participation in our project and 7 | our community a harassment-free experience for everyone, regardless of age, body 8 | size, disability, ethnicity, sex characteristics, gender identity and expression, 9 | level of experience, education, socio-economic status, nationality, personal 10 | appearance, race, religion, or sexual identity and orientation. 11 | 12 | ## Our Standards 13 | 14 | Examples of behavior that contributes to creating a positive environment 15 | include: 16 | 17 | * Using welcoming and inclusive language 18 | * Being respectful of differing viewpoints and experiences 19 | * Gracefully accepting constructive criticism 20 | * Focusing on what is best for the community 21 | * Showing empathy towards other community members 22 | 23 | Examples of unacceptable behavior by participants include: 24 | 25 | * The use of sexualized language or imagery and unwelcome sexual attention or 26 | advances 27 | * Trolling, insulting/derogatory comments, and personal or political attacks 28 | * Public or private harassment 29 | * Publishing others' private information, such as a physical or electronic 30 | address, without explicit permission 31 | * Other conduct which could reasonably be considered inappropriate in a 32 | professional setting 33 | 34 | ## Our Responsibilities 35 | 36 | Project maintainers are responsible for clarifying the standards of acceptable 37 | behavior and are expected to take appropriate and fair corrective action in 38 | response to any instances of unacceptable behavior. 39 | 40 | Project maintainers have the right and responsibility to remove, edit, or 41 | reject comments, commits, code, wiki edits, issues, and other contributions 42 | that are not aligned to this Code of Conduct, or to ban temporarily or 43 | permanently any contributor for other behaviors that they deem inappropriate, 44 | threatening, offensive, or harmful. 45 | 46 | ## Scope 47 | 48 | This Code of Conduct applies both within project spaces and in public spaces 49 | when an individual is representing the project or its community. Examples of 50 | representing a project or community include using an official project e-mail 51 | address, posting via an official social media account, or acting as an appointed 52 | representative at an online or offline event. Representation of a project may be 53 | further defined and clarified by project maintainers. 54 | 55 | ## Enforcement 56 | 57 | Instances of abusive, harassing, or otherwise unacceptable behavior may be 58 | reported by contacting the project team at grants@mintbase.io. All 59 | complaints will be reviewed and investigated and will result in a response that 60 | is deemed necessary and appropriate to the circumstances. The project team is 61 | obligated to maintain confidentiality with regard to the reporter of an incident. 62 | Further details of specific enforcement policies may be posted separately. 63 | 64 | Project maintainers who do not follow or enforce the Code of Conduct in good 65 | faith may face temporary or permanent repercussions as determined by other 66 | members of the project's leadership. 67 | 68 | ## Attribution 69 | 70 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, 71 | available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html 72 | 73 | [homepage]: https://www.contributor-covenant.org 74 | 75 | For answers to common questions about this code of conduct, see 76 | https://www.contributor-covenant.org/faq 77 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Apache License 2 | Version 2.0, January 2004 3 | http://www.apache.org/licenses/ 4 | 5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 6 | 7 | 1. Definitions. 8 | 9 | "License" shall mean the terms and conditions for use, reproduction, 10 | and distribution as defined by Sections 1 through 9 of this document. 11 | 12 | "Licensor" shall mean the copyright owner or entity authorized by 13 | the copyright owner that is granting the License. 14 | 15 | "Legal Entity" shall mean the union of the acting entity and all 16 | other entities that control, are controlled by, or are under common 17 | control with that entity. For the purposes of this definition, 18 | "control" means (i) the power, direct or indirect, to cause the 19 | direction or management of such entity, whether by contract or 20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 21 | outstanding shares, or (iii) beneficial ownership of such entity. 22 | 23 | "You" (or "Your") shall mean an individual or Legal Entity 24 | exercising permissions granted by this License. 25 | 26 | "Source" form shall mean the preferred form for making modifications, 27 | including but not limited to software source code, documentation 28 | source, and configuration files. 29 | 30 | "Object" form shall mean any form resulting from mechanical 31 | transformation or translation of a Source form, including but 32 | not limited to compiled object code, generated documentation, 33 | and conversions to other media types. 34 | 35 | "Work" shall mean the work of authorship, whether in Source or 36 | Object form, made available under the License, as indicated by a 37 | copyright notice that is included in or attached to the work 38 | (an example is provided in the Appendix below). 39 | 40 | "Derivative Works" shall mean any work, whether in Source or Object 41 | form, that is based on (or derived from) the Work and for which the 42 | editorial revisions, annotations, elaborations, or other modifications 43 | represent, as a whole, an original work of authorship. For the purposes 44 | of this License, Derivative Works shall not include works that remain 45 | separable from, or merely link (or bind by name) to the interfaces of, 46 | the Work and Derivative Works thereof. 47 | 48 | "Contribution" shall mean any work of authorship, including 49 | the original version of the Work and any modifications or additions 50 | to that Work or Derivative Works thereof, that is intentionally 51 | submitted to Licensor for inclusion in the Work by the copyright owner 52 | or by an individual or Legal Entity authorized to submit on behalf of 53 | the copyright owner. For the purposes of this definition, "submitted" 54 | means any form of electronic, verbal, or written communication sent 55 | to the Licensor or its representatives, including but not limited to 56 | communication on electronic mailing lists, source code control systems, 57 | and issue tracking systems that are managed by, or on behalf of, the 58 | Licensor for the purpose of discussing and improving the Work, but 59 | excluding communication that is conspicuously marked or otherwise 60 | designated in writing by the copyright owner as "Not a Contribution." 61 | 62 | "Contributor" shall mean Licensor and any individual or Legal Entity 63 | on behalf of whom a Contribution has been received by Licensor and 64 | subsequently incorporated within the Work. 65 | 66 | 2. Grant of Copyright License. Subject to the terms and conditions of 67 | this License, each Contributor hereby grants to You a perpetual, 68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 69 | copyright license to reproduce, prepare Derivative Works of, 70 | publicly display, publicly perform, sublicense, and distribute the 71 | Work and such Derivative Works in Source or Object form. 72 | 73 | 3. Grant of Patent License. Subject to the terms and conditions of 74 | this License, each Contributor hereby grants to You a perpetual, 75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 76 | (except as stated in this section) patent license to make, have made, 77 | use, offer to sell, sell, import, and otherwise transfer the Work, 78 | where such license applies only to those patent claims licensable 79 | by such Contributor that are necessarily infringed by their 80 | Contribution(s) alone or by combination of their Contribution(s) 81 | with the Work to which such Contribution(s) was submitted. If You 82 | institute patent litigation against any entity (including a 83 | cross-claim or counterclaim in a lawsuit) alleging that the Work 84 | or a Contribution incorporated within the Work constitutes direct 85 | or contributory patent infringement, then any patent licenses 86 | granted to You under this License for that Work shall terminate 87 | as of the date such litigation is filed. 88 | 89 | 4. Redistribution. You may reproduce and distribute copies of the 90 | Work or Derivative Works thereof in any medium, with or without 91 | modifications, and in Source or Object form, provided that You 92 | meet the following conditions: 93 | 94 | (a) You must give any other recipients of the Work or 95 | Derivative Works a copy of this License; and 96 | 97 | (b) You must cause any modified files to carry prominent notices 98 | stating that You changed the files; and 99 | 100 | (c) You must retain, in the Source form of any Derivative Works 101 | that You distribute, all copyright, patent, trademark, and 102 | attribution notices from the Source form of the Work, 103 | excluding those notices that do not pertain to any part of 104 | the Derivative Works; and 105 | 106 | (d) If the Work includes a "NOTICE" text file as part of its 107 | distribution, then any Derivative Works that You distribute must 108 | include a readable copy of the attribution notices contained 109 | within such NOTICE file, excluding those notices that do not 110 | pertain to any part of the Derivative Works, in at least one 111 | of the following places: within a NOTICE text file distributed 112 | as part of the Derivative Works; within the Source form or 113 | documentation, if provided along with the Derivative Works; or, 114 | within a display generated by the Derivative Works, if and 115 | wherever such third-party notices normally appear. The contents 116 | of the NOTICE file are for informational purposes only and 117 | do not modify the License. You may add Your own attribution 118 | notices within Derivative Works that You distribute, alongside 119 | or as an addendum to the NOTICE text from the Work, provided 120 | that such additional attribution notices cannot be construed 121 | as modifying the License. 122 | 123 | You may add Your own copyright statement to Your modifications and 124 | may provide additional or different license terms and conditions 125 | for use, reproduction, or distribution of Your modifications, or 126 | for any such Derivative Works as a whole, provided Your use, 127 | reproduction, and distribution of the Work otherwise complies with 128 | the conditions stated in this License. 129 | 130 | 5. Submission of Contributions. Unless You explicitly state otherwise, 131 | any Contribution intentionally submitted for inclusion in the Work 132 | by You to the Licensor shall be under the terms and conditions of 133 | this License, without any additional terms or conditions. 134 | Notwithstanding the above, nothing herein shall supersede or modify 135 | the terms of any separate license agreement you may have executed 136 | with Licensor regarding such Contributions. 137 | 138 | 6. Trademarks. This License does not grant permission to use the trade 139 | names, trademarks, service marks, or product names of the Licensor, 140 | except as required for reasonable and customary use in describing the 141 | origin of the Work and reproducing the content of the NOTICE file. 142 | 143 | 7. Disclaimer of Warranty. Unless required by applicable law or 144 | agreed to in writing, Licensor provides the Work (and each 145 | Contributor provides its Contributions) on an "AS IS" BASIS, 146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 147 | implied, including, without limitation, any warranties or conditions 148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 149 | PARTICULAR PURPOSE. You are solely responsible for determining the 150 | appropriateness of using or redistributing the Work and assume any 151 | risks associated with Your exercise of permissions under this License. 152 | 153 | 8. Limitation of Liability. In no event and under no legal theory, 154 | whether in tort (including negligence), contract, or otherwise, 155 | unless required by applicable law (such as deliberate and grossly 156 | negligent acts) or agreed to in writing, shall any Contributor be 157 | liable to You for damages, including any direct, indirect, special, 158 | incidental, or consequential damages of any character arising as a 159 | result of this License or out of the use or inability to use the 160 | Work (including but not limited to damages for loss of goodwill, 161 | work stoppage, computer failure or malfunction, or any and all 162 | other commercial damages or losses), even if such Contributor 163 | has been advised of the possibility of such damages. 164 | 165 | 9. Accepting Warranty or Additional Liability. While redistributing 166 | the Work or Derivative Works thereof, You may choose to offer, 167 | and charge a fee for, acceptance of support, warranty, indemnity, 168 | or other liability obligations and/or rights consistent with this 169 | License. However, in accepting such obligations, You may act only 170 | on Your own behalf and on Your sole responsibility, not on behalf 171 | of any other Contributor, and only if You agree to indemnify, 172 | defend, and hold each Contributor harmless for any liability 173 | incurred by, or claims asserted against, such Contributor by reason 174 | of your accepting any such warranty or additional liability. 175 | 176 | END OF TERMS AND CONDITIONS 177 | 178 | APPENDIX: How to apply the Apache License to your work. 179 | 180 | To apply the Apache License to your work, attach the following 181 | boilerplate notice, with the fields enclosed by brackets "[]" 182 | replaced with your own identifying information. (Don't include 183 | the brackets!) The text should be enclosed in the appropriate 184 | comment syntax for the file format. We also recommend that a 185 | file or class name and description of purpose be included on the 186 | same "printed page" as the copyright notice for easier 187 | identification within third-party archives. 188 | 189 | Copyright [yyyy] [name of copyright owner] 190 | 191 | Licensed under the Apache License, Version 2.0 (the "License"); 192 | you may not use this file except in compliance with the License. 193 | You may obtain a copy of the License at 194 | 195 | http://www.apache.org/licenses/LICENSE-2.0 196 | 197 | Unless required by applicable law or agreed to in writing, software 198 | distributed under the License is distributed on an "AS IS" BASIS, 199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 200 | See the License for the specific language governing permissions and 201 | limitations under the License. 202 | -------------------------------------------------------------------------------- /applications/DAOsign.md: -------------------------------------------------------------------------------- 1 | # Mintbase Grant Proposal 2 | 3 | - **Project Name:** DAOsign 4 | - **Team Name:** DAOsign 5 | - **Payment Address:** 0x793F7a7542c14088dbF58A19d2687FB9E7A79482 6 | - **[Level](../README.md#level_slider-levels):** 3 7 | 8 | ## Project Overview :page_facing_up: 9 | 10 | ### Overview 11 | 12 | DAOsign is a decentralized platform for agreements and automated workflows, with publicly verifiable, cryptographic proofs-of-signature, designed for DAOs and WEB3 companies. 13 | Verifiable Signature is at the core of DAOsign and is based on 3 key proofs: proof-of-identify, proof-of-authority, and proof-of-agreement. Utilizing these proofs, DAOsign provides a platform to design and configure complex workflows that combine smart-contract-based automation with authorized approvals. 14 | 15 | Our project seeks to enhance the Mintbase and NEAR ecosystem by providing an agreement-signing tool that empowers users to securely execute and manage agreements related to their NFT transactions. Through this integration, we aim to streamline processes, enhance user experience, and contribute to the growth and adoption of both Mintbase and NEAR. 16 | 17 | We were solving the problem for ourselves. Before DAOsign, our team was working as a blockchain consulting agency and we regularly had clients who didn't want to disclose their identities, so we were not able to sign any kind of legal agreements with them. Neither DocuSign nor other known solutions back to that time didn't help us to solve this problem. 18 | And after we wrote down our idea in detail and shared it with our clients, friends and partners, we got very positive feedback and realized that it was not only us who were in such a situation. 19 | 20 | ### Project Details 21 | 22 | - An overview of the technology stack to be used: [Pitch Deck](https://docsend.com/view/sbexkxn5su3ahdg8) 23 | - PoC/MVP or other relevant prior work or research on the topic: [One-pager](https://drive.google.com/file/d/1lDWNBoz18y11kARGxZpQrN_ca2muDmT7/view?usp=sharing) 24 | We would like to have a screening call with you and demo DAOsign, if appropriate 25 | 26 | ### Ecosystem Fit 27 | 28 | Our project plays a critical role within the Mintbase ecosystem by providing an agreement-signing tool for Mintbase users. It serves as an essential layer that enhances the transactional and contractual aspects of the NFT marketplace. By integrating our tool with Mintbase, users gain access to a streamlined and secure process for executing and managing agreements related to their NFT transactions. 29 | 30 | DAOsign has a user-friendly interface and is suitable for almost all users of the web3 industry with different purposes. 31 | 32 | The primary need that our project meets is the requirement for trust, transparency, and security in NFT transactions within Mintbase. With the increasing popularity of NFTs, it is crucial to have a robust system in place to handle the contractual aspects of these transactions. DAOsign addresses this need by providing a reliable and user-friendly solution for Mintbase users to create, sign, and manage agreements. 33 | 34 | We have two categories of competitors: legacy electronic signature tools such as DocuSign and web3 signature tools such as ethsign.xyz. We made some research and a more detailed competitive landscape can be found in our pitch deck. 35 | 36 | ## Team :busts_in_silhouette: 37 | 38 | ### Team members 39 | 40 | - Name of team leader: Eugene Fine (CEO & Founder) 41 | - Names of team members: Ramil Amerzyanov (CTO), Misha Kushka (Technical Lead), Sandra Burmenska (Business Development Director) 42 | 43 | ### Contact 44 | 45 | - **Contact Name:** Sandra Burmenska 46 | - **Contact Email:** sandra@daosign.org 47 | - **Website:** https://www.linkedin.com/in/oleksandra-burmenska/ 48 | 49 | ### Legal Structure 50 | 51 | - **Registered Address:** ILLINOIS LIMITED LIABILITY CORPORATION, USA 52 | - **Registered Legal Entity:** DAOSIGN, LLC 53 | 54 | ### Team's experience 55 | 56 | Eugene Fine (Founder & CEO). Former CTO for ExplorerSurgical, VP of engineering at https://www.explorersurgical.com/, tech advisor for https://polywrap.io/#/. CEO for https://daosign.org/, https://consideritdone.tech/. 57 | 58 | Ramil Amerzyanov (CTO). 12+ years in building complex enterprise solutions, contributor to https://github.com/cerc-io/go-ethereum/pull/31 and https://github.com/cosmos/ethermint-archive/pulls?q=is%3Apr+author%3Aramilexe+is%3Aclosed ecosystems. CTO for https://daosign.org/, https://consideritdone.tech/. 59 | 60 | Misha Kushka (Team Lead and Blockchain Developer). Blockchain expert with a solid tech background. Winner of Blockchain hackathons. Contributor to Tier1 blockchains. 61 | 62 | Oleksandra Burmenska (Business Development Director). Blockchain advisor with a tech background. Contributed to NEAR, Polywrap, Axelar, GnosisSafe, Avalanche ecosystems. 63 | 64 | During our work as a blockchain development agency, we contributed to almost all Tier 1 blockchains including: 65 | - contribution to the development of Ethereum standards 66 | - Polywrap wrappers for Axelar and NEAR 67 | - crypto wallet for the NEAR chain 68 | - Avalanche subnet and other Avalanche - based products 69 | - a lot of tools and solutions for Cosmos 70 | 71 | More information can be found here https://docsend.com/view/fjrvjtyzgm7wgrkj (our consulting portfolio) 72 | 73 | ### Team Code Repos 74 | 75 | - https://github.com/ConsiderItDone 76 | - https://github.com/ConsiderItDone/LandslideCore 77 | - https://github.com/ConsiderItDone/wasmos 78 | 79 | Please also provide the GitHub accounts of all team members. If they contain no activity, references to projects hosted elsewhere or live are also fine. 80 | 81 | - [Eugene Fine](https://github.com/ConsiderItDone) 82 | - [Ramil Amerzyanov](https://github.com/ramilexe) 83 | - [Misha Kushka](https://github.com/kushkamisha) 84 | - [Sandra Burmenska](https://github.com/burmenska) 85 | 86 | ### Team LinkedIn Profiles (if available) 87 | 88 | - [Eugene Fine](https://www.linkedin.com/in/eugenefine/) 89 | - [Ramil Amerzyanov](https://www.linkedin.com/in/ramil-amerzyanov/) 90 | - [Misha Kushka](https://www.linkedin.com/in/mkushka/) 91 | - [Sandra Burmenska](https://www.linkedin.com/in/oleksandra-burmenska/) 92 | 93 | ## Development Status :open_book: 94 | 95 | https://github.com/DAOsign 96 | 97 | ## Development Roadmap :nut_and_bolt: 98 | 99 | ### Overview 100 | 101 | - **Total Estimated Duration:** 6-8 months 102 | - **Full-Time Equivalent (FTE):** 4 FTE 103 | - **Total Costs:** 50,000 USD 104 | 105 | ### Milestone 1 — Mintbase Testnet Version 106 | 107 | - **Estimated duration:** 2 month 108 | - **FTE:** 4 109 | - **Costs:** 30,000 USD 110 | 111 | | Number | Deliverable | Specification | 112 | | -----: | ----------- | ------------- | 113 | | 0a. | License | Apache 2.0 | 114 | | 1. | The ability to store proofs on Mintbase Testnet blockchain and verify them there. | The functionality includes: “Create an agreement” implementation; Assigning signers and observers | 115 | | 2a. | Implementation of Proof-of-Authority | 116 | | 2b. | Implementation of Proof-of-Signature | 117 | | 2c. | Implementation of Proof-of-Agreement | 118 | | 3 | Early adopters program preparation | 119 | 120 | 121 | ### Milestone 2 — Incentivized Testnet version 122 | 123 | - **Estimated Duration:** 2 month 124 | - **FTE:** 4 125 | 126 | | Number | Deliverable | Specification | 127 | | -----: | ----------- | ------------- | 128 | | 0a. | License | Apache 2.0 | 129 | | 1. | Early Adopters Program launch | Adjusted roadmap based on Early Adopters' feedback | 130 | | 2. | Online onboarding events | 131 | | 3. | Feedback collecting | 132 | | 4. | Roadmap adjustment | 133 | 134 | 135 | ### Milestone 3 — Mainnet version 136 | 137 | - **Estimated Duration:** 3-4 month 138 | - **FTE:** 4 139 | - **Costs:** 15,000 USD 140 | 141 | | Number | Deliverable | Specification | 142 | | -----: | ----------- | ------------- | 143 | | 0a. | License | Apache 2.0 | 144 | | 1. | Launching blockchain-stored and verified proofs version of DAOsign | Publicly verifiable, flexible Signer Identity Verification System | 145 | | 2. | Production support System resiliency | 146 | | 3. | NFT-based Signer Authority Verification System | 147 | 148 | 149 | ### Milestone 4 — Mainnet version extended 150 | 151 | - **Estimated Duration:** 4 month 152 | - **FTE:** 4 153 | - **Costs:** 5,000 USD 154 | 155 | | Number | Deliverable | Specification | 156 | | -----: | ----------- | ------------- | 157 | | 0a. | License | Apache 2.0 | 158 | | 1. | Snapshot integration | Extended DAOsign version launch | 159 | | 2. | GPT3 integration | 160 | | 3. | Agreement legal templates | 161 | 162 | 163 | ## Future Plans 164 | 165 | In the near future, from the marketing side, we plan to attract users in these ways: 166 | 1. DAOs: 167 | first 1-3 months: contact all the DAOs we or our partners know. 168 | first 2-4 months: reaching TOP100 DAOs 169 | Starting from month 5: regularly check the new DAOs and contact them offering to use our product 170 | 2. Startups: 171 | same way as with DAOs 172 | 3. Participating in the web3 conferences and promoting DAOsign there 173 | 4. Organize side events/meetups for our potential target audience 174 | -------------------------------------------------------------------------------- /applications/Monad-Application.md: -------------------------------------------------------------------------------- 1 | # Mintbase Grant Proposal 2 | 3 | - **Project Name:** Monad NFT Multi-Chanel Gated Ticketing, Creator Minting and Marketplaces 4 | - **Team Name:** Monad.Social 5 | - **Payment Address:** monadsocial.near 6 | - **[Level](../README.md#level_slider-levels):** 2 7 | 8 | ## Project Overview :page_facing_up: 9 | 10 | ### Overview 11 | 12 | - Monad.Social is a subscription-based, virtual live performance streaming experience and community powered by web3 (Web3 version of Twitch for Music). 13 | - Monad.Social allows for creators to manage and monetize their own fanbase and offers a number of benefits for those fanbases from a variety of functional NFTs to Live Streaming performance, sophisticated chat and feeds, badging, community recognition and much more. For more information, see Monad deck: https://docs.google.com/presentation/d/1LgFlNbeyC9v7SMxqyp1zpqShieDY2Wk9A7NlELU-_Lg/edit?usp=sharing 14 | - As part of our prior NEAR Grant, we have implemented a basic NFT system for POAPs, tipping benefit and earning Monad FTs. Next steps are to scale, make creation easier, and a number of other improvements to the NFT system and its overall integration into our experience. A core part of our goal is to make these technologies have value for the average "fan", make it very easy to engage with and use, and drive greater creator/fan engagement and satisfaction (leading to continued subscription). 15 | - Monad's prior $75k NEAR Grant was to build out all the necessary infrastructure and to launch the World's First "dance to earn app" we call the Virtual Dance Floor. We use the gyro and accelerometer in mobile devices to translate dancing movements into pulsing avatars that earn Monad Tokens. Phase II of this roadmap is to integrate Mintbase in order to expand and improve the UX for both the Creators and Fans. We will implement the ability of Artist/Creators to directly upload their NFT art that will be used for sale of NFTs that purchased by fans as tips for music performance and POAPs. For more information on prior NEAR Grant, see Trello Board https://trello.com/b/VJ1pxt4j/near-grant-milestones 16 | - In addition we want all these NFTs to be searchable and discoverable by regular web search. We will also implement the ability for Fans earning Monad Tokens via the Virtual Dance Floor, and other user behaviours, to be able to spend these Monad Tokens to purchase NFTs and to tie all of this into a NFT Gated Ticketing solution that can be used both in Virtual Events andy by IRL Venues. 17 | - The goal here is to create an economic ecosystem here that drives customer acquisition and retention behaviour for the masses - not to create speculative assets. 18 | - In order to accomplish this, we need to make the UX, especially for Creators, as simple and intuitive as possible. In our discussions with Mintbase executives (Paul Kuveke and Nate Geieir), we believe in aggregate your solutions are the best option for us to achieve these goals. 19 | - These products and developments will allow us to complete the last step in this phase which is NFT Gated Ticking. Ticketing A Huge Problem in the music industry ecosystem in particular is the loss of control by the Artists/Creators once a ticket is Initially Sold. Many bots purchase tickets to be marked up tremendously then resold on StubHub, etc. Not only do “real fans” often miss the opportunity to purchase these tickets, which upsets all artists, but of course none this money for this ‘ticket scalping’ goes to the artist / creators / event producers. This is on top of the exorbitant fees charged by these ticketing services the vast majority of which is in the 30% to 50%+ range. Not only will we solve these problems, by using our Ticketing Platform as another extension of Tokenization, Gamification this will be another important element in customer acquisition and retention for Monad that will increase total revenues but not at the expense of artists, creators and our ticketing customers. 20 | - Completing this buildout will provide the foundation for the next phase of comleting our AR Virtual Venues Portals built on Unity with tokenizing and implementing these featues via the NEAR/Unity SDK (more below and in Trello). 21 | 22 | Adding Royalty Payments will further level the playing field for Ticket Sellers and will further drive transaction volume since these Sellers will even promote the opportunity to buy these secondary tickets via Monad/MB/NEAR Marketplace. 23 | 24 | ### Project Details 25 | - PoC/MVP or other relevant prior work or research on the topic: We have a complete, fully functioning MVP with customers and generating revenue now ($200+k with $14 Monthly ARPU). The UI/UX for users both on the front-end side and for Creators to upload art is already completed and live. We can provide access to any Mintbase/NEAR people since the content is behind a paywall. 26 | - https://monad.social/ 27 | 28 | - Documentation of core components, protocols, architecture, etc. to be deployed - See Trello Boards (https://trello.com/b/rYDEt1eP/mintbase-grant-milestones) 29 | 30 | - Mockups/designs of any UI components 31 | - Fan UX, Purchase of NFTs as tips, POAPs - https://monad.social/circle/djsneak/ 32 | - POAP Upload UI: https://monad.social/wp-content/uploads/2023/12/MonadSocial-Create-PoAP-NFT.png 33 | - NFTs for tipping: https://monad.social/wp-content/uploads/2023/12/MonadSocial-Create-Tipping-NFT.png 34 | - Data models / API specifications of the core functionality 35 | 36 | - An overview of the technology stack to be used 37 | - Smart Contracts: Rust, NEAR SDK, Mintbase API 38 | - Front End: React, HTML, CSS, JavaScript 39 | - Back End: We are Google Cloud for Startups Partner so all infrastructure on GCP with a WordPress MySQL DB. 40 | 41 | - Data models / API specifications of the core functionality: See Trello Boards (https://trello.com/b/rYDEt1eP/mintbase-grant-milestones) 42 | 43 | ### Ecosystem Fit 44 | 45 | - Where and how does your project fit into the ecosystem? 46 | - We had always planned after "Phase I" of our first NEAR Grant was to continue building out our Product Roadmap with NEAR and partners. After significant research and discussions with the Mintbase team, we believe this is the best solution for us to carry on with our roadmap since we have built substantial aspects of the underlying required architecture, it makes to continue building upon this foundation. 47 | - Who is your target audience (parachain/dapp/wallet/UI developers, designers, your own user base, some dapp's userbase, yourself)? 48 | - We have 2 target audiences - Music Creators and their Fans. Music Creators indcludes artist, record labels, festivals, and venues. We are working with one of the 3 Major Record labels amd other artists to help them migrate their 30 million YouTube subscribers to Monad. 49 | - What need(s) does your project meet? 50 | - We need to create simple, elegant solutions to lower the barriers for Creators and Fans to supply art that can be monetized through tokenization and digital asset sales. Then to in turn create entertaining Fan Experiences that will encourage usage and therefore be an excellent customer retention tool. We also see an opening in the market for a low cost NFT Gated Ticketing solution that will combine access to our Virtual Venues with IRL Venues. 51 | - Are there any other projects similar to yours in the Mintbase / NEAR ecosystem? 52 | - Sweatcoin has done something similar of course with the "exercise to earn" aspect of what we're doing. We are unaware of other Web3 versions of Twitch for Music which is what we are building out. 53 | 54 | ## Team :busts_in_silhouette: 55 | 56 | ### Team members 57 | 58 | - Brett Hawkins - CEO Product Lead 59 | - Greg Johnson - Chief Digital Strategist 60 | - Jiandon Wei - CTO 61 | - Anvar Bagiyev - Lead Designer/UI/UX 62 | 63 | ### Contact 64 | 65 | - **Contact Name:** Brett Hawkins 66 | - **Contact Email:** Brett@monad.social 67 | - **Website:** https://monad.social/ 68 | 69 | ### Legal Structure 70 | 71 | - **Registered Address:** 920 California Ave., Suite 3, Venice, CA 90291 72 | - **Registered Legal Entity:** Monad.Social PBC 73 | 74 | ### Team's experience 75 | 76 | In addition to the current Monad business and technology stack, our Team has been building complex, consumer facing internet applications together for over a decade (an individual careers all 20+ in tech). In addition to having received the prior NEAR Grant of $75,000 and completed that buildout, we are also a Google Cloud for Startups partner. This team built an early e-sports live streaming platform called Global Gaming League that we took from a napkin to 10 Million MAUs. We are applying a lot from that experience to apply video game and Web3 technologies to the music industry and broader. 77 | 78 | 79 | ### Team Code Repos 80 | 81 | - https://github.com/monadsocial 82 | - Project 1: https://github.com/monadsocial/NEAR-NFT 83 | - Project 2: https://github.com/monadsocial/Near-Tipping 84 | - Project 3: https://github.com/monadsocial/MonadFT 85 | 86 | ### Team LinkedIn Profiles 87 | 88 | - https://www.linkedin.com/in/bretthawkinsjr/ 89 | - https://www.linkedin.com/in/gregrjohnson/ 90 | - https://www.linkedin.com/in/jiandong-wei-3a602158/ 91 | - https://www.linkedin.com/in/anvarbagi/ 92 | 93 | ## Development Roadmap :nut_and_bolt: 94 | 95 | ### Overview 96 | Trello Board for Project 97 | (https://trello.com/b/rYDEt1eP/mintbase-grant-milestones) 98 | 99 | - **Total Estimated Duration:** 3.5 Months 100 | - **Full-Time Equivalent (FTE):** 3 FTE (Lead Engineer + Front End Engineer + UI/UX/Design + Strategy/Marketing, 7 people) 101 | - **Total Costs:** $45,000 102 | 103 | ### Milestone 1 - NFT Creation & Distribution Processes for Circles (channels) & Legacy NFT Integration (Trello First Card MS1: https://trello.com/c/j8usIwpQ) 104 | 105 | - **Estimated duration:** 1 month 106 | - **FTE:** 3 107 | - **Costs:** 15,000 USD 108 | 109 | ### Milestone 2 — NFT System Processes for User Profiles (Creators & Fans) & Marketplaces (Trello First Card MS2: https://trello.com/c/Exn1g1Xu) 110 | 111 | - **Estimated Duration:** 1 month 112 | - **FTE:** 3 113 | - **Costs:** 15,000 USD 114 | 115 | ### Milestone 3 — NFT Gated Ticketing System & Processes (Trello First Card MS3: https://trello.com/c/8bB46SKw) 116 | 117 | - **Estimated Duration:** 1.5 months 118 | - **FTE:** 3 119 | - **Costs:** 15,000 USD 120 | 121 | 122 | ## Future Plans 123 | 124 | The next steps in our 2024 Roadmap after completion of these milestones will include: 125 | 126 | - Complete the creation, buildout and infrastructure development for our Tokenizaed AR Portal Virtual Venues (video demo here: https://vimeo.com/861100716/1c938a25fd?share=copy ) including gamification via building out / customizing the Unity SDK for NEAR that carries over from the current Virtual Dance Floor App that’s already been built on NEAR. This will include earn and burn mechanics, use of NFT based Avatars, minting, tracking and allocating FTs in AR App and related gamification features and built to be compatible with AR/VR Headsets (though not required). 127 | 128 | - When Twitter / X SDK available for Crypto Payments (we don’t see access yet), add this to our payment alternative of PayPal, Stripe and we’re working with other payment processors like Pix in Brazil. 129 | 130 | - Further build out of NFT Gated Ticketing solutions to provide more features for IRL Venues combining their ticketing with Monad Virtual Venus and experiences. We see this as a very large opportunity and discussing desired Use Cases and features for our partners at Warner Music, festivals like Tomorrowalnd, ADE and others. 131 | 132 | ## Additional Information :heavy_plus_sign: 133 | 134 | **How did you hear about the Grants Program?** 135 | 136 | Mintbase directly as introduced by NEAR and mentioned above. 137 | 138 | - We have already received grants from NEAR $75k, Google Cloud for Startups $200k+ and Celo Camp $20k 139 | -------------------------------------------------------------------------------- /applications/PWXchange.md: -------------------------------------------------------------------------------- 1 | # Mintbase Grant Proposal 2 | 3 | - **Project Name:** PWX - Backed by Real Life 4 | - **Team Name:** Benefício.web3 5 | - **Payment Address:** obeneficio.near 6 | - **[Level](../README.md#level_slider-levels):** 2 7 | 8 | ## Project Overview :page_facing_up: 9 | This is the continuation of the PWX grant. 10 | 11 | ### Overview 12 | 13 | **Become the blueprint for Near Protocol / Mintbase Spirits Marketplaces Business IRL** 14 | PWX - Backed by Real Life 15 | PWX is a platform that allows independent whisky distilleries to use blockchain to manage and distribute their future whisky casks. 16 | PWX aims to improve the process of searching for and purchasing whisky casks by providing a more efficient and flexible marketplace for independent distilleries to sell their products directly to the final customer. 17 | With PWX, independent distilleries have the freedom to scale their operations and have greater control over their production and distribution. 18 | 19 | 20 | ### Project Details 21 | 22 | **B2C** 23 | Customer Support Solutions 24 | As an end customer, merging Digital Contract (Smart Contract) and Physical Contract ensure authenticity, ownership and assured by law – via Docusign connection. Logistics, storage/warehousing, and insurance of your cask are included. 25 | 26 | **B2B** 27 | Distillery Support Solutions 28 | At PWX, we are committed to revolutionizing the whisky industry for independent distilleries. With our cutting-edge blockchain solution, we provide tailored support to help your distillery flourish. 29 | Global Market Access: 30 | Leverage the power of blockchain to access a global market. PWX’s blockchain-backed platform allows you to showcase your unique products to a worldwide audience of whisky enthusiasts. 31 | 32 | **Customer Purchase Flow** 33 | 34 | ![alt text](https://pwxchange.com/wp-content/uploads/2023/12/pwx_flow.png) 35 | 36 | **Assigned Cask Value:** Each cask is assigned a value, and the NFT serves as the means of payment. 37 | 38 | **Issuance of Purchase Order:** Upon NFT purchase, PWX generates a purchase order for cask production, initiating the production process. 39 | 40 | **Purchase Contract with Distillery:** PWX enters into a purchase contract with the distillery, specifying the terms and conditions. 41 | 42 | **Sales Contract with End Customer:** After the purchase contract, PWX establishes a sales contract with the end customer, ensuring a smooth transition from production to sale. 43 | 44 | **Storage Contracts:** Simultaneously, PWX creates storage contracts between itself and the distillery, and another with the end customer. 45 | 46 | **Payment Structure:** Payments are initiated, including the cask value, maintenance fees, Mintbase fees, and production costs. 47 | 48 | **Calculate Net Sale Value:** Deduct production costs, Mintbase fees, and maintenance fees to determine the net sale value. 49 | 50 | **Revenue Distribution:** Distribute revenue to entities as per the agreed percentages. 51 | 52 | **Operational Maintenance:** Allocate x% of the revenue value for recurring revenue to support ongoing operational maintenance. 53 | 54 | **Secure Contract Execution:** Ensure the security and legality of all contracts by conducting them exclusively through DocuSign. 55 | 56 | 57 | ### Ecosystem Fit 58 | 59 | Where and how does PWX fit into the ecosystem IRL to become the blueprint for Near Protocol / Mintbase Spirits Marketplaces Business IRL 60 | 61 | This approach ensures a seamless and transparent user experience, benefiting both consumers and independent distilleries in the whisky industry. PWX - Backed by Real Life is poised to redefine the landscape of whisky cask transactions and enhance the overall industry ecosystem through its innovative solutions and collaborative framework. 62 | 63 | **Membership and Community** 64 | **Membership Benefits:** Advantages of joining PWX – Backed by Real Life, including access to an independent distillery community. 65 | **Forum and Community Section:** Space for distilleries to discuss industry topics, share experiences, and seek advice. 66 | **Event Calendar:** List upcoming whisky events, tastings, and festivals. 67 | **Distillery Showcases:** Opportunities for independent distilleries to participate and present their products at these events. 68 | 69 | **Immutable Records:** 70 | The blockchain records are immutable, meaning they cannot be altered or tampered with. Protects your distillery’s reputation and ensures the integrity of your brand. 71 | 72 | **Customer Engagement:** 73 | Blockchain also allows us to create engaging experiences for your customers. They can trace the journey of each bottle, and access information about the distillery, its history, and tasting notes with a simple scan of a QR code. 74 | 75 | **Collaboration Opportunities:** 76 | PWX fosters collaborations within its blockchain ecosystem. Partner with other distilleries, distributors, or retailers in our network to create special editions and exclusive releases. 77 | 78 | ## Team :busts_in_silhouette: 79 | 80 | ### Team members 81 | https://pwxchange.com/team/ 82 | 83 | ### Contact 84 | - **Contact Name:** Ricardo Nunes 85 | - **Contact Email:** ricardo@obeneficio.com 86 | - **Website:** https://obeneficio.com/ 87 | 88 | ### Legal Structure 89 | 90 | - **Registered Address:** Rua da Prata nº 80 5º andar direito 1100-420 Lisboa 91 | - **Registered Legal Entity:** O Benefício Existe Lda VAT number: 514 141 891 92 | 93 | ### Team's experience 94 | 95 | Previous project: PWX 96 | 97 | O Benefício Existe Lda VAT number: 514 141 891 98 | 99 | 100 | ### Team Code Repos 101 | 102 | - https://github.com/orgs/pwxchange/ 103 | 104 | Please also provide the GitHub accounts of all team members. If they contain no activity, references to projects hosted elsewhere or live are also fine. 105 | 106 | Ricardo Nunes: https://github.com/ricardocanbereached 107 | 108 | Paulo Fernandes: https://github.com/PauloMonteiroFernandes 109 | 110 | Pedro Velez: https://github.com/simasvelez 111 | 112 | ### Team LinkedIn Profiles 113 | 114 | Ricardo Nunes - https://www.linkedin.com/in/ricardocanbereached/ 115 | 116 | Paulo Fernandes – https://www.linkedin.com/in/paulo-fernandes-5726347/ 117 | 118 | Pedro Velez - https://www.linkedin.com/in/thepedrovelez/ 119 | 120 | ## Development Status :open_book: 121 | 122 | Available at https://pwxchange.com 123 | 124 | ## Development Roadmap :nut_and_bolt: 125 | 126 | We have a 4-week roadmap that outlines the phased development of PWX, ensuring a systematic and thorough approach to creating a visionary platform for independent whisky distilleries. Each phase contributes to the overarching goal of revolutionizing the user experience and enhancing transparency, security, and collaboration within the whisky industry. 127 | 128 | **Weeks 1-2:** Redesign Phase 129 | Draft initial platform design and user interface mock-ups. 130 | Incorporate feedback from stakeholders. 131 | Finalize the design and architecture of the PWX platform. 132 | 133 | **Weeks 2-3:** B2C Features Implementation 134 | Develop B2C features focusing on end-user transparency and security. 135 | 136 | **Weeks 2-3:** B2B Solutions Development 137 | Work on membership benefits and community features for distilleries. 138 | Develop a collaborative forum and community section. 139 | Implement distillery showcase functionality. 140 | 141 | **Weeks 3-4:** Advanced Blockchain Features 142 | Enhance blockchain transparency features. 143 | Implement smart contracts for automated distillery operations (upon buy). 144 | Develop immutable record functionality for brand integrity. 145 | 146 | **Weeks 3-4:** Testing, Refinement, and Relaunch Preparation 147 | Conduct comprehensive testing of all platform features. 148 | Gather stakeholders' feedback. 149 | Refine any identified issues and optimize performance. 150 | Post-Launch: Ongoing Maintenance and Update 151 | 152 | Estimated duration: 4 weeks 153 | FTE: 1 154 | Costs: 15,000 USD 155 | 156 | | Number | Deliverable | Specification | 157 | | -----: | ----------- | ------------- | 158 | | 0a. | License | Apache 2.0 | 159 | | 0b. | Documentation | We will provide basic documentation on how to customize the UI and a detailed backend tutorial | 160 | | 0d. | Docker | We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone. | 161 | | 0e. | Article | We will publish an **article** explaining the full workflow concepts 162 | | 1. | UI Module | New marketplace UI integrated with Mintbase wallet | 163 | | 2. | Backend Minter | Server-based minter (mint on demand on NFT purchase)| 164 | | 3. | Offchain Functionality | We will create the off-chain functionality to connect the smart contract with DocuSign. | 165 | | 4. | Marketplace Template | We will create a marketplace template with the front-end and back-end functionalities. | 166 | -------------------------------------------------------------------------------- /applications/Roketo-Mintbase-Integration.md: -------------------------------------------------------------------------------- 1 | # Mintbase Grant Proposal 2 | 3 | - **Project Name:** Roketo-Mintbase-Integration 4 | - **Team Name:** Roketo 5 | - **Payment Address:** roketo.sputnik-dao.near 6 | - **[Level](../README.md#level_slider-levels):** 3 7 | 8 | ## Project Overview :page_facing_up: 9 | 10 | ### Overview 11 | 12 | - Roketo is a finance platform for token streaming and recurring payment flows. 13 | - Token streaming means your funds come every second at a certain speed and your recipients can withdraw them at any moment. 14 | - By supporting this initiative, Mintbase is investing in data infrastructure for the entire NEAR ecosystem as well as ability to add utility to FT and NFT, activate users and increase revenue. 15 | - Roketo team is interested in the advent of mass adoption, therefore, Roketo focuses on the integration of the mechanics of streaming tokens into web3 projects. 16 | 17 | ### Project Details 18 | 19 | - [API specifications of the core functionality](https://docs.roke.to/docs/Guides/how-to-use-the-contract). 20 | - Technology stack to be used: Rust, Near, React 21 | 22 | ### Ecosystem Fit 23 | 24 | - Roketo increases the activity of your audience. 25 | - Right now, our target audience can be categorised in the following groups: 26 | 1. NFT creators, artists, 27 | 2. Airdrop senders, 28 | 3. Crypto developers (Web3 and Web2) 29 | - What need(s) does Roketo-Mintbase-Integration meet: 30 | 1. Roketo gives the a simple way to stream FT to an NFT holder with a tokenId. Feature will be realized from Roketo dApp interface. 31 | 2. Roketo gives an option to begin the stream on first transfer after mint. 32 | 33 | ## Team :busts_in_silhouette: 34 | 35 | ### Team members 36 | 37 | - Taras Dovgal - CEO 38 | - Vasilisa Versus - CTO 39 | - Dmitry Tupalov - Tech Lead 40 | - Vlad Dziarkach - Product Manager 41 | - Yahor Viarbitski - BizDev 42 | - Dmitry Boldyrev - Software Engineer 43 | - Ekaterina Zhdanova - Software Engineer 44 | - Dmitry Shcherbyna - UI/UX Designer 45 | - Svetlana Chernysheva - QA Engineer 46 | - Anna Balakhontseva - Account manager 47 | 48 | ### Contact 49 | 50 | - **Contact Name:** Vasilisa Versus 51 | - **Contact Email:** dcversus@roke.to 52 | - **Website:** https://www.roke.to/ 53 | 54 | ### Legal Structure 55 | 56 | - **Registered Address:** Intershore Chambers, Road Town, Tortola, British Virgin Islands 57 | - **Registered Legal Entity:** ROKETO LABS LTD 58 | 59 | ### Team's experience 60 | 61 | - Vasilisa Versus 62 | - Co-Founder and CTO at Roketo 63 | - Dmitry Tupalov 64 | - Fullstack developer and Tech lead at Roketo 65 | - Dmitry Boldyrev 66 | - Fullstack developer at Roketo 67 | 68 | ### Team Code Repos 69 | 70 | - https://github.com/roke-to 71 | 72 | - https://github.com/dcversus 73 | - https://github.com/zerobias 74 | 75 | ### Team LinkedIn Profiles (if available) 76 | 77 | - https://www.linkedin.com/in/dcversus/ 78 | - https://www.linkedin.com/in/vladislavderkach/ 79 | 80 | ## Development Status :open_book: 81 | 82 | We are in the process of describing the idea. 83 | 84 | ## Development Roadmap :nut_and_bolt: 85 | 86 | 1) Implement stream FT to an NFT holder feature 87 | 2) Implement an option to begin the stream on first transfer after mint 88 | 89 | ### Overview 90 | 91 | - **Total Estimated Duration:** 3,5 months 92 | - **Full-Time Equivalent (FTE):** 10 FTE 93 | - **Total Costs:** 25,000 USD 94 | 95 | ### Milestone 1 — Implement stream FT to an NFT holder feature (smart contract creation) 96 | 97 | - **Estimated duration:** 1 months 98 | - **FTE:** 10 99 | - **Costs:** 15,000 USD 100 | 101 | | Number | Deliverable | Specification | 102 | | -----: | ----------- | ------------- | 103 | | 0a. | License | MIT | 104 | | 0b. | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** | 105 | | 0c. | Testing Guide | Core functions will be fully covered by unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. | 106 | | 0d. | Docker | We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone. | 107 | | 0e. | Article | We will publish an article/workshop that explains how to use the streaming to NFT smart contract. | 108 | | 1. | Subscription widget: X | We will create a smart contract that will give the ability to start token streaming to the NFT owner | 109 | 110 | ### Milestone 2 — Implement stream FT to an NFT holder feature to Roketo dApp UI 111 | 112 | - **Estimated Duration:** 1 months 113 | - **FTE:** 10 114 | - **Costs:** 5,000 USD 115 | 116 | | Number | Deliverable | Specification | 117 | | -----: | ----------- | ------------- | 118 | | 0a. | License | MIT | 119 | | 0b. | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** | 120 | | 0c. | Testing Guide | Core functions will be fully covered by unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. | 121 | | 0d. | Docker | We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone. | 122 | | 0e. | Article | We will publish an article/workshop that explains how to use the streaming to NFT feature. | 123 | | 1. | Stream to NFT: X | We will create a tool in Roketo UI that will give the ability to start token streaming to the NFT owner | 124 | 125 | ### Milestone 3 — Implement an option to begin the stream on first transfer after mint 126 | 127 | - **Estimated Duration:** 2 months 128 | - **FTE:** 10 129 | - **Costs:** 5,000 USD 130 | 131 | | Number | Deliverable | Specification | 132 | | -----: | ----------- | ------------- | 133 | | 0a. | License | MIT | 134 | | 0b. | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** | 135 | | 0c. | Testing Guide | Core functions will be fully covered by unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. | 136 | | 0d. | Docker | We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone. | 137 | | 0e. | Article | We will publish an article/workshop that explains how to switch on the option to start the stream on first transfer after mint. | 138 | | 1. | Stream to NFT: X | We will create an option to begin the stream on first transfer after mint | 139 | 140 | ... 141 | ## Future Plans 142 | 143 | We have plans to: 144 | - We plan to contibute the guidelines. 145 | - Drive auditory around the stream FT to NFT feature. 146 | - Promote the FT to NFT streaming in GameDev community. 147 | - Support new integrations with recurrent payment system in crypto. 148 | 149 | ## Additional Information :heavy_plus_sign: 150 | 151 | **How did you hear about the Grants Program?** Personal recommendation from Taras Dovgal (Roketo CEO) 152 | -------------------------------------------------------------------------------- /applications/UML.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Mintbase/Grants-Program/df25f02ee74c6148124ca2d78ac44cd116f1a3a1/applications/UML.jpg -------------------------------------------------------------------------------- /applications/WalliD verification SDK Grant Proposal.md: -------------------------------------------------------------------------------- 1 | # WalliD verification SDK Grant Proposal 2 | 3 | - **Project Name:** WalliD verification SDK as Mintbase module 4 | - **Team Name:** WalliD S.A. 5 | - **Payment Address:** 7c5db8d0d80eec153e8ed78d2706224428ebdcab4c8103b8e676b697452c75d7 6 | - **[Level](../README.md#level_slider-levels):** 2 7 | 8 | ## Project Overview :page_facing_up: 9 | 10 | ### Overview 11 | 12 | ![dAPP use case mockup](https://drive.google.com/uc?id=1uIBR05V1uXzxzf-OTLpz0B9-CK98M_N-) 13 | 14 | 15 | WalliD is the aggregator toolkit of all ID protocols and networks, making it simple for WebApps to authenticate and verify users' digital IDs from multiple infrastructures through a single SDK connection. 16 | With WalliD Verifier SDK, WebApps and dAPPs are able to customise different trust and access levels for their users, based on the amount or quality of the Digital IDs and other assets provided (eg. Citizen ID, Twitter account, NEAR wallet address or token held within) and ensure this proof-of-ownership is based on wallet signatures. 17 | The SDK v1 is currently under development, after the architecture and main features have been detailed in a POC implemented within DocuSign during 2022. 18 | 19 | **The goal of the project desctibbed in this application is to:** 20 | - Integrate WalliD Verifier SDK features with MintBase toolkit, making it available as an authentication and ID verifier module through their own toolkit 21 | 22 | **With this project we intend to enrich the NEAR and MintBase ecosystems by providing a tool that nables NEAR dAPPS to:** 23 | - Implement reputation and trust systems for their users 24 | - Verify user's IDs and NEAR assets through NEAR wallets 25 | - Create different trust scores and access levels for their users based on ID and asset verifications. 26 | 27 | ### Project Details 28 | 29 | This project will combine WalliD’s verification features with Mintbase’s toolkit for NFT marketplace builders. 30 | With it, Mintbase will be able to provide a universal authentication and ID verification module that can be integrated in any NEAR dApp through their toolkit, adding up to potential scope of features to their community of developers. 31 | 32 | **Below is the depiction of the architecture components and the agents’ interaction with them:** 33 |

34 | 35 |

36 | 37 | 38 | **During this project, we will be building:** 39 | 40 | - Verification SDK config module features. See [mockups here](https://docs.google.com/presentation/d/1IPxpi3hZmU1jtTuG7j3T8mWPoA1FLxPh1CY-2SrWtgU/edit?usp=sharing) 41 | - OAuth, / ID verification component (adapted from WalliD wallet verification component already built). See [mockups here](https://docs.google.com/presentation/d/1GxYymkknA61B-BsJ1qzAMb2TLMvQK9g5WBkQB5B6fME/edit?usp=sharing) 42 | - Frontend libs for dAPP developers 43 | - NPM libs for Mintbase admins to install the module 44 | 45 | See detailed milestones and roadmap in the milestones in the appropriate chapter of this application 46 | 47 | ### Ecosystem Fit 48 | 49 | Help us locate your project in the Mintbase landscape and what problems it tries to solve by answering each of these questions: 50 | 51 | - **Where and how does your project fit into the ecosystem?:** As an ID verification module available to all dAPP builders through Mintbase toolkit. 52 | - **Who is your target audience (parachain/dapp/wallet/UI developers, designers, your own user base, some dapp's userbase, yourself)?** dAAPs building reputation systems, trust scores or in need to comply with ID verification and data processing regulations. 53 | **- What need(s) does your project meet?:** We try to solve the problem of trust and accountability while allowing users to keep their self-sovereignty 54 | **- Are there any other projects similar to yours in the Mintbase / NEAR ecosystem?:** Not that we're aware of 55 | ** - If not, are there similar projects in related ecosystems?** [Project Galaxy](https://galxe.com/galxeid) 56 | 57 | ## Team :busts_in_silhouette: 58 | 59 | ### Team members 60 | 61 | - Filipe Veiga (CEO) 62 | - Vitor Viana (CTO) 63 | - Beatriz Pereira (UX/UI) 64 | - Guilherme Arsénio (Full stack) 65 | 66 | ### Contact 67 | 68 | - **Contact Name:** Filipe da Cruz Esteves Casal da Veiga 69 | - **Contact Email:** filipe.veiga@wallid.io 70 | - **Website:** [WalliD](https://wallid.io/) 71 | 72 | ### Legal Structure 73 | 74 | - **Registered Address:** Rua Fernanda Seno, nr 6, 7005-485, Évora, Portugal 75 | - **Registered Legal Entity:** WalliD S.A 76 | 77 | ### Team's experience 78 | 79 | Filipe and Vitor both met while working the development of Digital infrastructures in Portugal and have a background in product development of PKI based infrastrcutures, middleware and cryptography. Guilherme and Beatriz joined the team in 2019 when we first started building WalliD and have been the builders of all the teck stack already developed by WalliD. 80 | 81 | 82 | ### Team Code Repos 83 | 84 | - [WalliD](https://github.com/walliDprotocol) 85 | - [WalliD Wallet](https://github.com/walliDprotocol/WalliD-Wallet) 86 | - [WalliD POC with DocuSign ](https://github.com/walliDprotocol/NFT-Proof-of-Signature) 87 | 88 | Please also provide the GitHub accounts of all team members. If they contain no activity, references to projects hosted elsewhere or live are also fine. 89 | 90 | - [Filipe Veiga](https://github.com/FCVeiga) 91 | - [Vitor Viana ](https://github.com/masterviana) 92 | - [Guilherme Arsénio](https://github.com/GuilhermeArsenio) 93 | 94 | ### Team LinkedIn Profiles (if available) 95 | 96 | - [Filipe Veiga ](https://www.linkedin.com/in/fiveiga/) 97 | - [Vitor Viana ](https://www.linkedin.com/in/vviana/) 98 | - [Beatriz Pereira](https://www.linkedin.com/in/beatrizpereira215/) 99 | - [Guilherme Arsénio ](https://www.linkedin.com/in/guilherme-ars%C3%A9nio-4b6a1a148/) 100 | 101 | ## Development Status :open_book: 102 | 103 | Apart from conceptualizing the architecture of the SDK and building the mockups, we have implemented some of the integrations with Oauths (Twitter, Discord, Reddit, Githuub) and digital IDs (Portuguese Digital ID, LUKSO network) in WalliD wallet. 104 | 105 | ## Development Roadmap :nut_and_bolt: 106 | 107 | ### Overview 108 | 109 | - **Total Estimated Duration:** 10 weeks 110 | - **Full-Time Equivalent (FTE):** 4 111 | - **Total Costs:** 20,000 USD 112 | 113 | 114 | ### Milestone 1 — Verification connector 115 | 116 | - **Estimated duration:** 6 weeks 117 | - **FTE:** 4 118 | - **Costs:** 15,000 USD 119 | 120 | | Number | Deliverable | Specification | 121 | | -----: | ----------- | ------------- | 122 | | 1. | Connector API service | Integrates with OAuth protocols from web2 providers such as twitter, discord, github google, facebook, reddit and github. Implements NEAR Wallet authentication, NEAR tokens verification, NEAR social and connects to digital ID providers connected to WalliD ecosystem such as Chave Móvel Digital | 123 | | 2. | Documentation | Tecnical documentation, setup samples, | 124 | | 3. | Tests | Unit Tests | 125 | 126 | 127 | ### Milestone 2 — SDK NPM lib 128 | 129 | - **Estimated Duration:** 4 weeks 130 | - **FTE:** 4 131 | - **Costs:** 5,000 USD 132 | 133 | 134 | | Number | Deliverable | Specification | 135 | | -----: | ----------- | ------------- | 136 | | 1. | NPM Lib part 1 | Javascript section of the lib to implement operations supported by the verification connector. Allows users to authorize using NEAR wallets, OAuth protocols and digital ID protocols connected to WalliD's ecosystem. Supports admin operations for setup module. | 137 | | 2. | NPM Lib part 2 | Vuejs, React section of the lib to implement the already configured Verification connector on client dApp frontends | 138 | | 3. | Testing guide | coverage tests, unit tests | 139 | | 4. | Documentation | Tecnical documentation, coverage test, pratical samples, build instructions | 140 | 141 | 142 | ... 143 | ## Future Plans 144 | 145 | We intend to pilot test our Verifier aggregator value proposition amongst Web3 dAPPs with this grant and expand the reach of the SDK within the NEAR and other ecosystems by building a SaaS business model on top if. The integration and business development that will follow from the POC will the be the determing data points to espablish the way we will scale the business 146 | 147 | 148 | ## Additional Information :heavy_plus_sign: 149 | 150 | **How did you hear about the Grants Program?** Mintbase team 151 | -------------------------------------------------------------------------------- /applications/WalliD-MPC-Infra: -------------------------------------------------------------------------------- 1 | # WalliD MPC Infra Proposal 2 | 3 | - **Project Name:** WalliD MPC Infra 4 | - **Team Name:** WalliD S.A. 5 | - **Payment Address:** 7c5db8d0d80eec153e8ed78d2706224428ebdcab4c8103b8e676b697452c75d7 6 | - **[Level](../README.md#level_slider-levels):** 2 7 | 8 | ## Project Overview :page_facing_up: 9 | 10 | ### Overview 11 | 12 | WalliD is a Digital ID provider, focused on building an aggregator toolkit to enable users and organizations to issue, manage and prove the ownership of all types of verifiable data. 13 | Out tech stack is comprised of authentication, data verification, verifiable credential issuance and wallet solutions with corporate, web3 and governmental partners and customers. 14 | Our infraestructure is already connected to NEAR and our tools support NEAR wallets, token standards and smart contract queries. In this grant we intend to expand the level of integration and enrich the ecosystem by building a decentralized layer of access to the existing NEAR MPC infrastructure. 15 | 16 | **The goal of the project desctibbed in this application is to:** 17 | - Enable existing NEAR wallets to use NEAR MPC infra. 18 | - Create a NEAR MPC SDK for the ecosystem developers. 19 | - Build a relayer to decentralize the key distributions 20 | 21 | ### Project Details 22 | 23 | With this project WalliD is proposing to create a layer to add features to the the multi-party computing (MPC) infrastructure already built on [NEAR](https://github.com/near/mpc-recovery) in order to enable existing users to benefit from it, and developers to offer it as service within their own solutions. 24 | 25 | **Below is the depiction of the architecture components and related operations 26 |

27 | 28 |

29 | 30 | 31 | **During this project, we will be building:** 32 | 33 | - A Storage component to the NEAR MPC infra to support existing keys and add social logins as auth factor 34 | - A Recovery component to enable key recoveries with existing NEAR accounts and social logins 35 | - An SDK with frontend libs to use these features with NEAR MPC. 36 | - a decentralized relayer to distribute the key storage and assembly. 37 | 38 | See detailed milestones and roadmap in the milestones in the appropriate chapter of this application 39 | 40 | ### Ecosystem Fit 41 | 42 | Help us locate your project in the Mintbase landscape and what problems it tries to solve by answering each of these questions: 43 | 44 | - **Where and how does your project fit into the ecosystem?:** As an ID and wallet provider 45 | - **Who is your target audience (parachain/dapp/wallet/UI developers, designers, your own user base, some dapp's userbase, yourself)?** NEAR dApps that want to provide secure solutions to their users or to onboard users from outside the web3. 46 | **- What need(s) does your project meet?:** We're building ID solutions while focusing on the privacy and safety of data. 47 | **- Are there any other projects similar to yours in the Mintbase / NEAR ecosystem?:** Not that we're aware of 48 | ** - If not, are there similar projects in related ecosystems?** [Project Galxe](https://galxe.com/galxeid), [Web3auth](https://web3auth.io/docs/) 49 | 50 | ## Team :busts_in_silhouette: 51 | 52 | ### Team members 53 | 54 | - Filipe Veiga (CEO) 55 | - Vitor Viana (CTO) 56 | - Beatriz Pereira (UX/UI) 57 | - Guilherme Arsénio (Full stack) 58 | 59 | ### Contact 60 | 61 | - **Contact Name:** Filipe da Cruz Esteves Casal da Veiga 62 | - **Contact Email:** filipe.veiga@wallid.io 63 | - **Website:** [WalliD](https://wallid.io/) 64 | 65 | ### Legal Structure 66 | 67 | - **Registered Address:** Rua Fernanda Seno, nr 6, 7005-485, Évora, Portugal 68 | - **Registered Legal Entity:** WalliD S.A 69 | 70 | ### Team's experience 71 | 72 | Filipe and Vitor both met while working the development of Digital infrastructures in Portugal and have a background in product development of PKI based infrastrcutures, middleware and cryptography. Guilherme and Beatriz joined the team in 2019 when we first started building WalliD and have been the builders of all the teck stack already developed by WalliD. 73 | 74 | 75 | ### Team Code Repos 76 | 77 | - [WalliD](https://github.com/walliDprotocol) 78 | - [Social Logins for NEAR](https://github.com/walliDprotocol/verification-sdk-demo-app) 79 | - [eSignatures with wallets on DocuSign ](https://github.com/walliDprotocol/NFT-Proof-of-Signature) 80 | 81 | Please also provide the GitHub accounts of all team members. If they contain no activity, references to projects hosted elsewhere or live are also fine. 82 | 83 | - [Filipe Veiga](https://github.com/FCVeiga) 84 | - [Vitor Viana ](https://github.com/masterviana) 85 | - [Guilherme Arsénio](https://github.com/GuilhermeArsenio) 86 | 87 | ### Team LinkedIn Profiles (if available) 88 | 89 | - [Filipe Veiga ](https://www.linkedin.com/in/fiveiga/) 90 | - [Vitor Viana ](https://www.linkedin.com/in/vviana/) 91 | - [Beatriz Pereira](https://www.linkedin.com/in/beatrizpereira215/) 92 | - [Guilherme Arsénio ](https://www.linkedin.com/in/guilherme-ars%C3%A9nio-4b6a1a148/) 93 | 94 | ## Development Status :open_book: 95 | 96 | Idea and mockup stage. 97 | 98 | ## Development Roadmap :nut_and_bolt: 99 | 100 | ### Overview 101 | 102 | - **Total Estimated Duration:** 10 weeks 103 | - **Full-Time Equivalent (FTE):** 4 104 | - **Total Costs:** 20,000 USD 105 | 106 | 107 | ### Milestone 1 — MPC Store and Recovery features 108 | 109 | - **Estimated duration:** 2 weeks 110 | - **FTE:** 4 111 | - **Costs:** 10,000 USD 112 | 113 | | Number | Deliverable | Specification | 114 | | -----: | ----------- | ------------- | 115 | | 1. | API (Store Flow) | Will allow a n/3 solution (NEAR accounts, social accounts and OTP) to authenticate on NEAR MPC and enable existing NEAR accounts to generate an MPC key | 116 | | 2. | API (Recovery Flow) | Will allow to get the MPC key through a n/3 recovery system (NEAR accounts, social accounts and OTP) | 117 | | 3. | Documentation | Tecnical documentation, setup samples | 118 | | 4. | Tests | Unit Tests | 119 | 120 | 121 | ### Milestone 2 — MPC SDK 122 | 123 | - **Estimated Duration:** 6 weeks 124 | - **FTE:** 4 125 | - **Costs:** 10,000 USD 126 | 127 | 128 | | Number | Deliverable | Specification | 129 | | -----: | ----------- | ------------- | 130 | | 1. | SDK Libs (Store + Revoery requests)| Frontend libs to allow developers to easily connect with the API built on Milestone 1 and provide MPC features from their own environments| 131 | | 2. | Documentation | Tecnical documentation, coverage test, pratical samples, build instructions | 132 | | 3. | Testing guide | coverage tests, unit tests | 133 | 134 | 135 | ### Milestone 3 — MPC Relayer 136 | 137 | - **Estimated Duration:** 4 weeks 138 | - **FTE:** 4 139 | - **Costs:** 15,000 USD 140 | 141 | 142 | | Number | Deliverable | Specification | 143 | | -----: | ----------- | ------------- | 144 | | 1. | Relayer infra | |API to Assemble stored key, sign object and host a relay UR. | 145 | | 3. | Testing guide | coverage tests, unit tests | 146 | | 4. | Documentation | Tecnical documentation, coverage test, pratical samples, build instructions | 147 | ... 148 | ## Future Plans 149 | 150 | The goal of this project is to provide a tool for the NEAR ecosystem of developers to ensure their users have secure ways to backup and recover keys as well as to pay for user fees when desired. We plan to connect with teams in the ecosystem to test and improve the solution once an MVP is complete. 151 | 152 | ## Additional Information :heavy_plus_sign: 153 | 154 | **How did you hear about the Grants Program?** Mintbase team. We were in the cohort of the 1st season of Mintbase grants. 155 | -------------------------------------------------------------------------------- /applications/allies-marketplace.md: -------------------------------------------------------------------------------- 1 | # Mintbase Grant Proposal 2 | **Project Name:** "Allie's Marketplace" 3 | 4 | **Team Name:** Marmaj DAO 5 | 6 | **Payment Address**: marmaj.sputnik-dao.near 7 | 8 | **Level:** 1 9 | 10 | 11 | ## Project Overview :page_facing_up: 12 | 13 | ### Overview 14 | **A tag line:** Adult-centric NFT marketplace 18+ 15 | 16 | **Project description:** Allie’s Marketplace is an NFT marketplace built on NEAR Protocol. This is a hub for Allie’s own content and where her fans can buy her NFTs. The marketplace will also offer a variety of other content, including: videos, photos, and articles from Allie. The marketplace will be open to anyone who wants to purchase Allie’s content, and all transactions will be processed on the blockchain. This will provide a secure and efficient way for Allie to sell her content and connect with her fans. 17 | 18 | 19 | 20 | **Goal:** 21 | 22 | 23 | 24 | Our goal is to encourage web3 space adoption and utilisation by not-safe-for-work (NSFW) content producers through the development of a user-friendly and engaging NFT marketplace. 25 | 26 | 27 | 28 | Since our software is open source, anyone can use it to create their own decentralised marketplace. For creators who struggle to make money on centralised platforms and do not have full control over their content, this will be incredibly helpful. Because the marketplaces built on this code will be decentralised, they will also be shielded from censorship. 29 | 30 | 31 | 32 | The planned flow is as follows: 33 | 1) users go to the website and connect their wallets* to purchase NFTs and gain access to the content; 34 | 2) they can then make offers on the NFTs listed; 35 | 3) following the conclusion of the bidding, the buyer receives ownership of the NFT. If the user does not have a wallet, there will be the ability to create one instantly. 36 | 37 | 38 | 39 | 40 | **An indication of how your project relates to / integrates into the Mintbase / NEAR ecosystem:** 41 | 42 | 43 | 44 | This project relates to Mintbase and the NEAR ecosystem because it will allow not only Allie, but any other adult content creators the ability to spin up their needed tools in a decentralised manner. 45 | 46 | 47 | 48 | **An indication of why your team is interested in creating this project:** 49 | 50 | 51 | 52 | We are interested because we see how many creators are at the mercy of centralised platforms to distribute their content. The goal is to provide open source tools to support all creators, starting with one special creator. 53 | 54 | 55 | 56 | 57 | 58 | ### Project Details: 59 | 60 | 61 | 62 | **Flow Chart Diagram:** 63 | 64 | ![UML Design](./UML.jpg) 65 | 66 | **Technology stack:** 67 | - Backend: 68 | - MongoDB 69 | 70 | - AWS S3 (For censored content storage) 71 | 72 | - Express.js 73 | 74 | - Node.js 75 | 76 | - Near javascript-sdk (for smart contract) 77 | 78 | - Arweave (For NFT Pass Storage) 79 | 80 | 81 | 82 | - Frontend: 83 | 84 | - React 85 | 86 | - Tailwind CSS 87 | 88 | ### Ecosystem Fit 89 | 90 | **Where and how does your project fit into the ecosystem?** 91 | Right on top of Mintbase (as well as other Dapps hopefully). As people learn about Mintbase and the tools offered in the Mintbase toolkit, we hope that content creators looking for more delicate handling of their projects will look at this project. 92 | 93 | 94 | **Who is your target audience (parachain/dapp/wallet/UI developers, designers, your own user base, some dapp's user base, yourself)?** 95 | 96 | Target audience is generally NSFW content creators to spin up and use our contracts as well as consumers of the content who will be collecting NFTs. 97 | 98 | We also hope to integrate with various chains to ensure that funds can reach intended creators from any chain. 99 | 100 | **What need(s) does your project meet?** 101 | The need for open source web3 tools that support NSFW content creators. 102 | 103 | **If so, how is your project different?** 104 | 105 | Our project hopes to focus specifically on the sensitive nature of NSFW content creation and aims to focus on helping these creators use web3 tools to create self-sustaining economies for themselves. 106 | 107 | **If not, are there similar projects in related ecosystems?** 108 | Not that we have seen so far. 109 | 110 | ## Team 111 | 112 | **Team leader:** Chole Lewis 113 | **Team members:** Monish Muralidharan, Vijay Murugan, Allie Knox 114 | 115 | **Contact name:** Chole Lewis 116 | **Contact Email:** [chloe@marmaj.org](mailto:chloe@marmaj.org) 117 | 118 | 119 | **Team Code Repos:** 120 | 121 | 122 | 123 | 124 | 125 | 126 | 127 | - https://github.com/Kalankendra-DAO 128 | 129 | 130 | 131 | - https://github.com/MarmaJFoundation 132 | 133 | 134 | 135 | 136 | 137 | - https://github.com/Kalankendra-DAO/shardible 138 | 139 | ## Development Status: 140 | 141 | Our initiative is still in its early stages. We couldn't locate anything similar to this project since it is a new concept in this chain. Our requirements must be better considered and created. 142 | 143 | 144 | 145 | The development of this marketplace is complex as it is a new concept. First the project needs to be designed and planned. Then the necessary infrastructure has to be put in place. Once the marketplace is up and running it has to be properly marketed to its potential users. In order to ensure the success all these processes have to be met. 146 | 147 | ## Development Roadmap: 148 | 149 | ### Overview 150 | 151 | 152 | 153 | 154 | 155 | 156 | 157 | - **Total Estimated Duration:** 1.5 months 158 | 159 | 160 | 161 | 162 | 163 | - **Full-Time Equivalent (FTE):** 2.5 FTE 164 | 165 | 166 | 167 | 168 | 169 | - **Total Costs:** 10,000 USD 170 | 171 | ### Milestone 1 - Implement smart contract and backend 172 | 173 | 174 | 175 | 176 | 177 | 178 | 179 | - **Estimated duration:** 2-3 weeks 180 | 181 | 182 | 183 | 184 | 185 | - **FTE:** 2.5 FTE 186 | 187 | 188 | 189 | 190 | 191 | - **Costs:** 6,000 USD 192 | 193 | | Number | Deliverable | Specification | 194 | | -----: | ----------- | ------------- | 195 | | 0a. | License | MIT | 196 | | 0b. | Documentation | We will provide inline documentation of the code how a user can use our factory contract for their marketplace. And how to set the code in the cloud. | 197 | | 1. | Create account| Allie can update her Profile. | 198 | | 2. | Create Collection | To create a collection that stores the censored content in a centralised database and NFT in NEAR and Arweave.| 199 | | 3. | To unlock the content to the user | This function is to check if the connected wallet has any NFT of collection to unlock the content to that account.| 200 | 201 | 202 | ### Milestone 2 — Enhanced Frontend and User Adoption 203 | 204 | 205 | 206 | 207 | 208 | 209 | - **Estimated Duration:** 4 weeks 210 | 211 | 212 | 213 | 214 | 215 | - **FTE:** 2 216 | 217 | 218 | 219 | 220 | 221 | - **Costs:** 4,000 USD 222 | 223 | | Number | Deliverable | Specification | 224 | | -----: | ----------- | ------------- | 225 | | 0a. | License | MIT| 226 | | 0b. | Documentation | Provide mockups and/or wireframes (e.g. Figma) 227 | 228 | And documents on how to connect and buy and unlock the content of Allie’s (other content creator) | 229 | 230 | 231 | ### Future Plans: 232 | 233 | - The marketplace offers the owner Roketo payment services 234 | 235 | 236 | 237 | 238 | - The marketplace offers fundamental minting on Mintbase 239 | 240 | 241 | 242 | 243 | - For a lot of the front end and restricted content, we could even be able to collaborate with Gorilla Shops. 244 | 245 | 246 | 247 | 248 | - The marketplace offers organisational structure through Astro DAO (investment through tokens + Ref Finance). 249 | 250 | 251 | 252 | 253 | Thus, all the necessary instruments are already in place, but need to be linked together. If we can accomplish that, we will attract more people and, in the long run, establish this model as a platform. 254 | 255 | ### Additional Information: 256 | 257 | **How did you hear about the Grants Program?:** 258 | 259 | 260 | 261 | From Twitter and being active in the NEAR Ecosystem. 262 | -------------------------------------------------------------------------------- /applications/application-gorilla-shops-automat.md: -------------------------------------------------------------------------------- 1 | # Mintbase Grant Proposal 2 | 3 | - **Project Name:** Gorilla Shops - Batch Minter Automat 4 | - **Team Name:** Gorilla Funds UG 5 | - **Payment Address:** gorillashops.near 6 | - **[Level](../README.md#level_slider-levels):** 2 7 | 8 | ## Project Overview :page_facing_up: 9 | 10 | ### Overview 11 | 12 | Gorilla Shops is building the Batch-Minting-Tool "Automat". This Batch-Minting-Tool will provide an easy solution to mint and list collections just by uploading a well formed zip-File. This will make it easy to mint thousands of NFTs on Mintbase just with a few clicks. 13 | 14 | ### Project Details 15 | 16 | The Tool will consists of two parts. An open API and a User Interface. The API will be open for everyone to use and the User Interface will be easy to add into your own project. The User Interface will be easy to customize so that it can be used by everyone, who wants to add this additional functionality to their DApps. 17 | The Tool is in the first round designed to work best with Gorilla Shops Figma Plug-In Unikat. In the second iteration it will be generalized to make minting of batches and performing batch transactions like transfering of NFTs or Airdrops of NFTs way more easy like it is now. 18 | 19 | ### Ecosystem Fit 20 | 21 | Help us locate your project in the Mintbase landscape and what problems it tries to solve by answering each of these questions: 22 | 23 | - Where and how does your project fit into the ecosystem? 24 | 25 | Automat is a usefull tool to help all projects that want to work with larger amounts of NFTs. Especially it is helpfull for creators of NFT collections. 26 | 27 | - Who is your target audience (parachain/dapp/wallet/UI developers, designers, your own user base, some dapp's userbase, yourself)? 28 | 29 | We target Mintbase users that want to leverage Mintbase for minting collections or bigger amounts of NFTs. 30 | 31 | - What need(s) does your project meet? 32 | 33 | The API and the User Interface targets Mintbase Store owners that want to produce NFTs in larger amounts as they want to mint collections of unikats or thousands of NFTs. 34 | 35 | - Are there any other projects similar to yours in the Mintbase / NEAR ecosystem? 36 | 37 | As the project is designed to use with the Figma-Plugin their is right now no similar project out there. 38 | 39 | - If so, how is your project different? 40 | 41 | ## Team :busts_in_silhouette: 42 | 43 | ### Team members 44 | 45 | - CEO: Jakob Sievers 46 | 47 | - Developers: 48 | 49 | - Sascha Metz (Full Stack) 50 | - Tobias Metz (Front End) 51 | - Jonas Hartweg (Front End, UI/UX-Expert) 52 | - Valentin Hehl (Security, Backend) 53 | 54 | - Designer: 55 | 56 | - Reimar Servas 57 | 58 | - Consultancy (Design Systems, Bridging Design and Code) 59 | 60 | - Reimar Servas 61 | 62 | - Product Management: 63 | - Aymie Laipe 64 | 65 | ### Contact 66 | 67 | - **Contact Name:** Jakob Sievers 68 | - **Contact Email:** Jakob.Sievers@gorillashops.io 69 | - **Website:** https://gorillashops.io 70 | 71 | ### Legal Structure 72 | 73 | - **Registered Address:** Hermann-Wellensiek-Strasse 33, 67346 Speyer 74 | - **Registered Legal Entity:** Gorilla Funds UG, Hermann-Wellensiek-Strasse 33, 67346 Speyer 75 | 76 | ### Team's experience 77 | 78 | All Team members are experienced in their field as can be seen by our product. 79 | 80 | - Jakob Sievers: Jakob Sievers is a former teacher for physics, chemistry and computer science. Founded the Gorilla Funds UG in 2020. I discovered the blockchain space in 2012 and got caught since then in the rabbit hole. Coding experience 15+ years. 81 | - Reimar Servar: Reimar Servas is a Freelance consultant. Designer/Developer, early browser wars veteran. Working on systems and processes for humans, connecting programmers and designers. 82 | - Tobias Metz: Tobias Metz is an full stack software engineer from south-west germany. He had worked in several  web-agencies  and hardware/network B2B company’s as well. He has an information technology background and ~10 years of customer/developer experience. 83 | - Sascha Metz: Sascha Metz started building websites in 2012, is developing for a living since 2015. Started with "classic" WordPress Websites but nowadays i am all into the JAM-Stack. Also pretty enthusiastic about cloud computing, especially with AWS. 84 | - Jonas Hartweg: Jonas Hartweg is a frontend engineer living in Berlin. He has ten years of development experience and worked for big B2B companies as well as smaller media agencies. Next to his work as a developer, he is currently finishing his M.A. in product design. 85 | - Valentin Hehl: Valentin Hehl is a Computer Science student at the KIT University Karlsruhe and 21 years old. He was in the winning team of the European cyber security challenge in 2019 in the category _Junior_. 86 | - Aymie Laipe: Aymie is our product manager and organizes our overall collaboration. 87 | 88 | ### Team Code Repos 89 | 90 | - https://github.com/gorillafunds 91 | 92 | Right now the repository is private. We will provide all necessary access to the repository to the Mintbase team. 93 | 94 | Github-Repositories of the Team-Members: 95 | 96 | - https://github.com/gorillafunds 97 | 98 | Tobias Metz 99 | 100 | - https://github.com/tmtz 101 | 102 | Sascha Metz 103 | 104 | - https://github.com/smetzdev 105 | 106 | Jonas Hartweg 107 | 108 | - https://github.com/johnny353535 109 | 110 | Reimar Servas 111 | 112 | - https://github.com/reimar 113 | 114 | Valentin Hehl 115 | 116 | - https://github.com/ZTube 117 | 118 | Jakob Sievers 119 | 120 | - https://github.com/gorillafund 121 | 122 | Team Code Repos 123 | Right now the Team Code Repo is private. We have to pull some things out as we are working with a mono-repo structure, 124 | as this repository also contains our corporate site code 125 | 126 | - https://github.com/gorillafund/gorilla-technologies 127 | 128 | ### Team LinkedIn Profiles 129 | 130 | - Jakob Sievers: https://www.linkedin.com/in/jakob-sievers-97579b201/ 131 | - Reimar Servas: https://www.linkedin.com/in/reimarservas/ 132 | - Jonas Hartweg: https://www.linkedin.com/in/jonas-hartweg-66272449/ 133 | - Sascha Metz: No LinkedIn 134 | - Tobias Metz: No LinkedIn 135 | - Valentin Hehl: No LinkedIn 136 | - Aymie Laipe: https://www.linkedin.com/in/aymie-laipe/ 137 | 138 | ## Development Status :open_book: 139 | 140 | The User inferface design is finished. This is how it will look like: 141 | 142 | https://youtu.be/nsCMwNvmtgk 143 | 144 | Right now we are building the components and the flow. The API is functional as well, but is not open accessible right now. 145 | 146 | ## Development Roadmap :nut_and_bolt: 147 | 148 | ### Overview 149 | 150 | - **Total Estimated Duration:** 3 Months 151 | - **Full-Time Equivalent (FTE):** 4 FTE 152 | - **Total Costs:** 50000 US$ 153 | 154 | ### Milestone 1: Release MVP: 155 | 156 | - **Estimated duration:** 2 month 157 | - **FTE:** 4 158 | - **Costs:** 35,000 USD 159 | 160 | | Number | Deliverable | Specification | 161 | | -----: | -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | 162 | | 0a. | License | MIT | 163 | | 0b. | Documentation | We will provide both **inline documentation** of the code and a basic **video tutorial** that explains how Automat works. | 164 | | 0c. | Testing Guide | Core functions will be fully covered by **unit tests** to ensure functionality and robustness. In the guide, we will describe how to run these tests. | 165 | | 0d. | Testnet-API instance | We will provide a **Testnet-API-Instance** that can be used to test all the functionalites of our product. | 166 | | 0e. | Article | We will publish an **article** that explains all features and how to use Automat. | 167 | | 1. | API | The API allow **minting, listing or burning of every amount of NFTs** on a store if our wallet has minted the NFTs. You can also transfer the ownership of any of these minted NFTs | 168 | | 2. | User-Interface | The User-Interface allows **easy minting of thousands of NFTs** where the necessary images and information are uploaded within a zipped folder. | 169 | 170 | ### Milestone 2: Make it production ready: 171 | 172 | This will include the following features 173 | 174 | - Perform User-Tests to make the tool as user friendly as possible. 175 | - Publish a npm-package for easy integration of Automat. 176 | - Add detailed documentation 177 | - Perform security and performance tests 178 | 179 | - **Estimated duration:** 1 month 180 | - **FTE:** 4 181 | - **Costs:** 15,000 USD 182 | 183 | | Number | Deliverable | Specification | 184 | | -----: | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | 185 | | 0a. | License | MIT | 186 | | 0b. | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how a user has to interact with Automat | 187 | | 0c. | Testing Guide | Core functions will be fully covered by unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. | 188 | | 0d. | Testnet-Instance | We will provide a Testnet-Instance that can be used to test all the functionalites of our product. | 189 | | 0e. | Article | We will publish an **article** that explains all features and how to use them as well as two-weekly development updates in our discord-channel. | 190 | 191 | ## Clarifications 192 | 193 | The Code for the User Interface will be released under MIT-License. The backend code is not part of this proposal. The API-will be open for anyone to use who is the owner of a store on Mintbase. 194 | 195 | ## Future Plans 196 | 197 | The next part of "Automat" will be a generalized version, that allows way more options for the minting operation of the NFTs, like individual options per NFT. Minting of thousands of just one NFT and way more.The following version will also add an easy white-label solution that can easily be integrated in your very own web app. 198 | 199 | ## Additional Information :heavy_plus_sign: 200 | 201 | **How did you hear about the Grants Program?** From the Mintbase-Team 202 | -------------------------------------------------------------------------------- /applications/application_template.md: -------------------------------------------------------------------------------- 1 | # Mintbase Grant Proposal 2 | 3 | > This document will be part of the terms and conditions of your agreement and therefore needs to contain all the required information about the project. Don't remove any of the mandatory parts presented in bold letters or as headlines. Blockquote sections starting with a `>` (such as this one) can be removed. 4 | > 5 | > See the [Grants Program Process](https://github.com/Mintbase/Grants-Program/#pencil-process) on how to submit a proposal. 6 | 7 | - **Project Name:** Name of your project (e.g. DuoSwap Module) 8 | - **Team Name:** Legal name of your team (e.g. Duo) 9 | - **Payment Address:** A NEAR account to where funds can be transfered (e.g. myproject.near) 10 | - **[Level](../README.md#level_slider-levels):** 1, 2 or 3 11 | 12 | > ⚠️ *The combination of your GitHub account submitting the application and the payment address above will be your unique identifier during the program. Please keep them safe.* 13 | 14 | ## Project Overview :page_facing_up: 15 | 16 | If this application is in response to an RFP, please indicate this on the first line of this section. 17 | 18 | If this is an application for a follow-up grant (the continuation of an earlier, successful Mintbase grant), please provide name and/or pull request of said grant on the first line of this section. 19 | 20 | ### Overview 21 | 22 | Please provide the following: 23 | 24 | - If the name of your project is not descriptive, a tag line (one sentence summary). 25 | - A brief description of your project. 26 | - An indication of how your project relates to / integrates into the Mintbase / NEAR ecosystem. 27 | - An indication of why your team is interested in creating this project. 28 | 29 | ### Project Details 30 | 31 | We expect the teams to already have a solid idea about your project's expected final state. Therefore, we ask the teams to submit (where relevant): 32 | 33 | - Mockups/designs of any UI components 34 | - Data models / API specifications of the core functionality 35 | - An overview of the technology stack to be used 36 | - Documentation of core components, protocols, architecture, etc. to be deployed 37 | - PoC/MVP or other relevant prior work or research on the topic 38 | - What your project is _not_ or will _not_ provide or implement 39 | - This is a place for you to manage expectations and to clarify any limitations that might not be obvious 40 | 41 | ### Ecosystem Fit 42 | 43 | Help us locate your project in the Mintbase landscape and what problems it tries to solve by answering each of these questions: 44 | 45 | - Where and how does your project fit into the ecosystem? 46 | - Who is your target audience (parachain/dapp/wallet/UI developers, designers, your own user base, some dapp's userbase, yourself)? 47 | - What need(s) does your project meet? 48 | - Are there any other projects similar to yours in the Mintbase / NEAR ecosystem? 49 | - If so, how is your project different? 50 | - If not, are there similar projects in related ecosystems? 51 | 52 | ## Team :busts_in_silhouette: 53 | 54 | ### Team members 55 | 56 | - Name of team leader 57 | - Names of team members 58 | 59 | ### Contact 60 | 61 | - **Contact Name:** Full name of the contact person in your team 62 | - **Contact Email:** Contact email (e.g. john@duo.com) 63 | - **Website:** 64 | 65 | ### Legal Structure 66 | 67 | - **Registered Address:** Address of your registered legal entity, if available. Please keep it in a single line. (e.g. High Street 1, London LK1 234, UK) 68 | - **Registered Legal Entity:** Name of your registered legal entity, if available. (e.g. Duo Ltd.) 69 | 70 | ### Team's experience 71 | 72 | Please describe the team's relevant experience. If your project involves development work, we would appreciate it if you singled out a few interesting projects or contributions made by team members in the past. For research-related grants, references to past publications and projects in a related domain are helpful. 73 | 74 | If anyone on your team has applied for a grant at the Mintbase previously, please list the name of the project and legal entity here. 75 | 76 | ### Team Code Repos 77 | 78 | - https://github.com/ 79 | - https://github.com// 80 | - https://github.com// 81 | 82 | Please also provide the GitHub accounts of all team members. If they contain no activity, references to projects hosted elsewhere or live are also fine. 83 | 84 | - https://github.com/ 85 | - https://github.com/ 86 | 87 | ### Team LinkedIn Profiles (if available) 88 | 89 | - https://www.linkedin.com/ 90 | - https://www.linkedin.com/ 91 | 92 | ## Development Status :open_book: 93 | 94 | If you've already started implementing your project or it is part of a larger repository, please provide a link and a description of the code here. In any case, please provide some documentation on the research and other work you have conducted before applying. This could be: 95 | 96 | - links to improvement proposals or [RFPs](https://github.com/mintbase/Grants-Program/tree/master/rfp-proposal) (requests for proposal), 97 | - academic publications relevant to the problem, 98 | - links to your research diary, blog posts, articles, forum discussions or open GitHub issues, 99 | - references to conversations you might have had related to this project with anyone from the Mintbase Foundation, 100 | - previous interface iterations, such as mock-ups and wireframes. 101 | 102 | ## Development Roadmap :nut_and_bolt: 103 | 104 | This section should break the development roadmap down into milestones and deliverables. To assist you in defining it, we have created a document with examples for some grant categories [here](../docs/grant_guidelines_per_category.md). Since these will be part of the agreement, it helps to describe _the functionality we should expect in as much detail as possible_, plus how we can verify and test that functionality. Whenever milestones are delivered, we refer to this document to ensure that everything has been delivered as expected. 105 | 106 | Below we provide an **example roadmap**. In the descriptions, it should be clear how your project is related to Mintbase. We _recommend_ that teams structure their roadmap as 1 milestone ≈ 1 month. 107 | 108 | For each milestone, 109 | 110 | - make sure to include a specification of your software. _Treat it as a contract_; the level of detail must be enough to later verify that the software meets the specification. 111 | - include the amount of funding requested _per milestone_. 112 | - include documentation (tutorials, API specifications, architecture diagrams, whatever is appropriate) in each milestone. This ensures that the code can be widely used by the community. 113 | - provide a test suite, comprising unit and integration tests, along with a guide on how to set up and run them. 114 | - commit to providing Dockerfiles for the delivery of your project. 115 | - indicate milestone duration as well as number of full-time employees working on each milestone. 116 | - **Deliverables 0a-0d are mandatory for all milestones**, and deliverable 0e at least for the last one. If you do not intend to deliver one of these, please state a reason in its specification (e.g. Milestone X is research oriented and as such there is no code to test). 117 | 118 | > :zap: If any of your deliverables is based on somebody else's work, make sure you work and publish _under the terms of the license_ of the respective project and that you **highlight this fact in your milestone documentation** and in the source code if applicable! **Teams that submit others' work without attributing it will be immediately terminated.** 119 | 120 | ### Overview 121 | 122 | - **Total Estimated Duration:** Duration of the whole project (e.g. 2 months) 123 | - **Full-Time Equivalent (FTE):** Average number of full-time employees working on the project throughout its duration (see [Wikipedia](https://en.wikipedia.org/wiki/Full-time_equivalent), e.g. 2 FTE) 124 | - **Total Costs:** Requested amount in USD for the whole project (e.g. 12,000 USD). Note that the acceptance criteria and additional benefits vary depending on the [level](../README.md#level_slider-levels) of funding requested. This and the costs for each milestone need to be provided in USD; if the grant is paid out in USN, and potentially NEAR and nUSDC, the amount will be calculated according to the exchange rate at the time of payment. 125 | 126 | ### Milestone 1 Example — Implement Mintbase Modules 127 | 128 | - **Estimated duration:** 1 month 129 | - **FTE:** 2 130 | - **Costs:** 8,000 USD 131 | 132 | | Number | Deliverable | Specification | 133 | | -----: | ----------- | ------------- | 134 | | 0a. | License | Apache 2.0 / GPLv3 / MIT / Unlicense | 135 | | 0b. | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how a user can (for example) spin up one of our Mintbase nodes and send test transactions, which will show how the new functionality works. | 136 | | 0c. | Testing Guide | Core functions will be fully covered by unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. | 137 | | 0d. | Docker | We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone. | 138 | | 0e. | Article | We will publish an **article**/workshop that explains [...] (what was done/achieved as part of the grant). (Content, language and medium should reflect your target audience described above.) 139 | | 1. | Mintbase module: X | We will create a Mintbase / NEAR module that will... (Please list the functionality that will be implemented for the first milestone) | 140 | | 2. | Mintbase module: Y | We will create a Mintbase / NEAR module that will... | 141 | | 3. | Mintbase module: Z | We will create a Mintbase / NEAR module that will... | 142 | | 4. | NEAR chain integration | Modules X, Y & Z of our custom chain will interact in such a way... (Please describe the deliverable here as detailed as possible) | 143 | 144 | 145 | ### Milestone 2 Example — Additional features 146 | 147 | - **Estimated Duration:** 1 month 148 | - **FTE:** 1 149 | - **Costs:** 4,000 USD 150 | 151 | ... 152 | ## Future Plans 153 | 154 | Please include here 155 | 156 | - how you intend to use, enhance, promote and support your project in the short term, and 157 | - the team's long-term plans and intentions in relation to it. 158 | 159 | 160 | ## Additional Information :heavy_plus_sign: 161 | 162 | **How did you hear about the Grants Program?** Mintbase Website / Medium / Twitter / Element / Announcement by another team / personal recommendation / etc. 163 | 164 | Here you can also add any additional information that you think is relevant to this application but isn't part of it already, such as: 165 | 166 | - Work you have already done. 167 | - If there are any other teams who have already contributed (financially) to the project. 168 | - Previous grants you may have applied for. -------------------------------------------------------------------------------- /applications/lightofEarendil.md: -------------------------------------------------------------------------------- 1 | 2 | - **Project Name:** Light of Eärendill 3 | - **Team Name:** Jeeltcraft 4 | - **Payment Address:** jilt.near 5 | - **[Level](../README.md#level_slider-levels):** 1 6 | 7 | > ⚠️ *The combination of your GitHub account submitting the app&lication and the payment address above will be your unique identifier during the program. Please keep them safe.* 8 | 9 | ## Project Overview :page_facing_up: 10 | 11 | This is a follow up project for the Varda Vault unlockable content project launch, the Vault was funded by humanguild.io. The light of Eãrendil is built to engage the blender.org 3D creative community in minting on the near Blockchain using the mintbase standard smart contract and the Varda Vault unlockable content service directly from the blender 3D editor interface. 12 | ### Overview 13 | 14 | Please provide the following: 15 | 16 | - A python addon for the open source blender UI to mint a 3D render and lock the source file as unlockable content. 17 | - Blender files are db files full of reusable assets for people to reproduce the rendered art, by selling a render and locking the corresponding .blend file you share your creative solution along with the nft. The market for this solutions on gumroad is very spread and used around the world. 18 | - This project is built to spread news about the mintbase minting platform and smart contracts AND the varda vault in a creative community that has been growing and thriving for almost two decades, a community of creators that is used to spread news through YouTube channels and Twitter accounts if they like an addon, 19 | people have built businesses on suggesting the right addon for blender (example https://blender-addons.org/) 20 | 21 | ### Project Details 22 | 23 | To develop the python addon we plan to use the [Serpens addon](https://blendermarket.com/products/serpens) for the blender scripting interface: 24 | - [Importing](https://drive.google.com/file/d/1rPy4Gn2a-q89NF56scdsaJdBHfnIu7s8/view?usp=drivesdk) the [near python API](https://github.com/near/near-api-py) and trigger the standard [minting action on a mintbase contract](https://drive.google.com/file/d/1QtwZ_iCDoYQR1joiodVZRX_RCmnjg2x5/view?usp=drivesdk), the minting action would be fired after the rendering has finished and the user has logged in with a [simple button located in one of these standard positions](https://drive.google.com/file/d/1cEowRRnfi4PKBXf4L4or7RneG171D6T7/view?usp=drivesdk) on the blender interface, triggering a web login. 25 | - To lock the source content on the Varda Vault we would implement a specific locking endpoint on the [varda vault API](https://github.com/jilt/Vault-API-Filecoin) and the data importing options ([1](https://drive.google.com/file/d/1sjVCX1BqLhvBf4ol52P_lt_cxrRL_WjD/view?usp=drivesdk) and [2](https://drive.google.com/file/d/1haCCWKAEPzMxbU5MLmOLCyhgI_qLBzfq/view?usp=drivesdk)) of the Serpens graphical scripting interface. 26 | - Mintbase basic core functions [reference](https://github.com/Mintbase/mb-sdk), the user has to create his own smart contract on mintbase or be an allowed contributor of an already existing one. 27 | - We are willing to submit the final addon in the blender market (they have a quite long selection process to be allowed to sell), gumroad and Serpens stores along with minting a mintbase nft on the jiltverse store with the addon as unlockable content. The whole developing rpocess will be finished by the end on October, because I'm November the #nodevember twitter creative challenge starts for the blender community and we wish to use our addon to create content for the whole challenge/month and use it to spread word of this new tool within the blender community. 28 | Price will be 1$ on the stores were free download is not allowed, and money earned will go to a newly created DAO to support artists thatint with our solution. 29 | 30 | 31 | ### Ecosystem Fit 32 | 33 | Help us locate your project in the Mintbase landscape and what problems it tries to solve by answering each of these questions: 34 | 35 | - Where and how does your project fit into the ecosystem? Unlockable nft content/nft utility 36 | - Who is your target audience? 37 | - integration of mintbase smart contracts with [one of the most used 3D editing interface in the world](www.blender.org). 38 | - Are there any other projects similar to yours in the Mintbase / NEAR ecosystem? 39 | - If not, are there similar projects in related ecosystems? No, the blender community has tried to breach the Blockchain using tezos but it didn't work... 40 | 41 | ## Team :busts_in_silhouette: 42 | 43 | ### Team members 44 | 45 | - Laura Camellini 46 | 47 | ### Contact 48 | 49 | - **Contact Name:** Laura Camellini 50 | - **Contact Email:** Contact email (e.g. jeeltcraft@gmail.com) 51 | - **Website:** www.jeeltcraft.com 52 | 53 | ### Legal Structure 54 | 55 | - **Registered Address:** Address of your registered legal entity, via Montegrappa 89 41132 Modena Italy 56 | - **Registered Legal Entity:** Laura Camellini VAT number IT03764030361 57 | 58 | ### Team's experience 59 | 60 | I just finished my very first [nft marketplace interface](https://nft.varda.vision) and custom nft smart contract with rust on near, I have experience with geometry nodes to [create art](https://paras.id/token/x.paras.near::51477/51477%3A1) for the nodevember challenge and with python as you can see from my TARDIS repository (last project a time machine for the Dropbox API) 61 | Although the varda vault unlockable content project is using the mintbase API I never applied for mintbase grants before 62 | ### Team Code Repos 63 | 64 | - https://github.com/jilt 65 | 66 | 67 | ### Team LinkedIn Profiles (if available) 68 | 69 | - https://www.linkedin.com/jeeltcraft 70 | 71 | ## Development Status :open_book: 72 | Not yet started 73 | 74 | ## Development Roadmap :nut_and_bolt: 75 | 76 | As per the links provided in the description 77 | Milestone 1: Addon development 78 | - timing: 1 month 79 | - result: downloadable links on gumroad, Serpens marketplace and mintbase/varda-vault with the python addon and a video to explain how to use it with the mintbase interface. 80 | 81 | This section should break the development roadmap down into milestones and deliverables. To assist you in defining it, we have created a document with examples for some grant categories [here](../docs/grant_guidelines_per_category.md). Since these will be part of the agreement, it helps to describe _the functionality we should expect in as much detail as possible_, plus how we can verify and test that functionality. Whenever milestones are delivered, we refer to this document to ensure that everything has been delivered as expected. 82 | 83 | Below we provide an **example roadmap**. In the descriptions, it should be clear how your project is related to Mintbase. We _recommend_ that teams structure their roadmap as 1 milestone ≈ 1 month. 84 | 85 | ### Overview 86 | 87 | - **Total Estimated Duration:** 1 month 88 | - **Full-Time Equivalent (FTE):** 1 FTE plus about 2 freelance "helpers" 89 | - **Total Costs:** 10,000 USD 90 | 91 | ### Milestone 1 Development 92 | 93 | - **Estimated duration:** 1 month 94 | - **FTE:** 1 95 | - **Costs:** 10,000 USD 96 | 97 | | Number | Deliverable | Specification | 98 | | -----: | ----------- | ------------- | 99 | | 1. | License |MIT 100 | 101 | ## Future Plans 102 | 103 | Please include here 104 | The Varda project aims to collaborate on and create an a reliable investing and service point for high level art and nfts on the near ecosystem, the Varda vault is built on the graph in order for queries to be the main source of tokens to sustain the project, we are waiting for the graph to be available as a decentralized network for the near Blockchain in order to achieve that, meanwhile we keep building on a decentralized data model and to share tools with the near creative community. 105 | 106 | 107 | ## Additional Information :heavy_plus_sign: 108 | 109 | **How did you hear about the Grants Program?** Twitter, Luis, Nate and Caroline <3 110 | 111 | Here you can also add any additional information that you think is relevant to this application but isn't part of it already, such as: 112 | 113 | - Work you have already done. 114 | - If there are any other teams who have already contributed (financially) to the project. 115 | - Previous grants you may have applied for. 116 | -------------------------------------------------------------------------------- /applications/metronomo.md: -------------------------------------------------------------------------------- 1 | # Mintbase Grant Proposal 2 | 3 | - **Project Name:** Metronomo 4 | - **Team Name:** Metronomo Team 5 | - **Payment Address:** metronomo.near 6 | - **[Level](../README.md#level_slider-levels):** 2 7 | 8 | ## Project Overview :page_facing_up: 9 | 10 | ### Overview 11 | [Metronomo](https://metronomo.xyz/) is a cross-chain user growth infrastructure 12 | 13 | #### Problem 14 | We asked a bunch of web3 projects about their biggest challenges. All of them mentioned user acquisition as an urgent issue. 15 | Our first approach was to build "HubSpot for web3". But from the very beginning, we faced two problems: 16 | 1. On-chain data is fragmented and poorly structured to create user profiles 17 | 2. ETL and mapping are resource intensive and expensive 18 | 19 | #### Solution 20 | To resolve these challenges, we decided to create a basic data layer for marketing teams and web3 builders. It will: 21 | - structure and combine on-chain data into users, projects, interactions, and other relevant dimensions 22 | - provide API to access and manage data 23 | - give fundamental technologies for building martech products (e.g., NFT recommendation and personalization system, matching web2 and web3 user data, zero, 1st, 2nd & 3rd party data system, knowledge and social graph, and others) 24 | 25 | #### Why we do 26 | - Our team has 10+ years of experience in digital marketing, data science, development, and data engineering. 27 | - We are highly confident that on-chain data has a significant role in scaling web3 products and the ecosystem as a whole. 28 | - So we see our mission as **make web3 martech great by the next bull run** 29 | 30 | ### Project Details 31 | 32 | We will deliver easy to use API, which allows functional integration in different products (ex., Mintbase UI, Telegram Bot, and others) 33 | - API specification: https://www.notion.so/metronomo/Projects-with-potential-power-users-7982033da4424787993fed3001a7f54a 34 | - MVP: Telegram bot: [@metronomo_bot](https://t.me/metronomo_bot) 35 | - Technology stack to be used: Google Cloud Functions, Google Cloud Storage, Python 36 | 37 | ### Ecosystem Fit 38 | #### Where and how does your project fit into the ecosystem? 39 | We see Metronomo as the user growth module of Mintbase now and part of marketplace contract 2.0 in the next iteration. 40 | 41 | #### Who is your target audience (parachain/dapp/wallet/UI developers, designers, your own user base, some dapp's userbase, yourself)? 42 | Mintbase ecosystem projects 43 | 44 | #### What need(s) does your project meet? 45 | As part of the marketplace contract 2.0, allow merchants to create product selections based on user profiles and similarity to other projects to grow revenue. 46 | 47 | #### Are there any other projects similar to yours in the Mintbase / NEAR ecosystem? 48 | All existing NEAR products cover a single aspect of user growth but are not open-source infrastructure. 49 | (e.g., Wombi - dashboards, Datrics - creating ML models, Plex - user profiling and engaging) 50 | 51 | #### If so, how is your project different? 52 | We build an open-source user growth infrastructure protocol. 53 | 54 | #### If not, are there similar projects in related ecosystems? 55 | 0xscope, The Graph, Permission.io, and other infrastructure products are close but not entirely similar. 56 | They are focused on general indexing issues but not on marketing data needs. 57 | 58 | ## Team :busts_in_silhouette: 59 | 60 | ### Team members 61 | 62 | - Vladimir Gusev (team leader) 63 | - Yaroslav Bondarchuk 64 | - Vadim Smirnov 65 | 66 | ### Contact 67 | 68 | - **Contact Name:** Vladimir Gusev 69 | - **Contact Email:** vladimir@metronomo.xyz 70 | - **Website:** https://metronomo.xyz/ 71 | 72 | ### Legal Structure 73 | 74 | - **Registered Address:** - 75 | - **Registered Legal Entity:** - 76 | 77 | ### Team's experience 78 | **Vladimir Gusev**: 79 | 80 | - co-Founder and CEO at [Metronomo](https://metronomo.xyz/) 81 | - ex-Partner & VP of Growth and later COO at [GigAnt - largest Workforce-as-a-Service marketplace in CIS](https://gigwork.ru/) 82 | - Company was successfully acquired by [Avito - World's Most-visited Classified Ads Site by Similarweb](https://www.yahoo.com/lifestyle/avito-named-world-most-visited-190600803.html) 83 | - ex-Co-founder and CMO at Russia's TOP10 Digital Marketing Agency 84 | - Company was successfully acquired by the TOP1 digital marketing group 85 | - ex-Professional online poker player from 2005 till 2010 86 | 87 | 88 | **Yaroslav Bondarchuk** 89 | 90 | 8+ years in analytics, data science, and data engineering: 91 | - co-Founder and CPO at [Metronomo](https://metronomo.xyz/) 92 | - ex-Head of analytics at [GigAnt - largest Workforce-as-a-Service marketplace in CIS](https://gigwork.ru/) 93 | - ex-Product owner at [Retail Rocket](https://retailrocket.net/) (recommender system product) 94 | - ex-Head of analytics at [Skillbox - leading edtech platform in Eastern Europe](https://skillbox.com/) 95 | 96 | **Vadim Smirnov** 97 | 98 | 9+ years in marketing and product growth: 99 | - co-Founder and CMO at [Metronomo](https://metronomo.xyz/) 100 | - ex-Head of growth at [GigAnt - largest Workforce-as-a-Service marketplace in CIS](https://gigwork.ru/) 101 | - Advisor at [Sailplay - international marketing automation platform](https://sailplay.com/) 102 | - ex-Performance marketing group head at [Skillbox - leading edtech platform in Eastern Europe](https://skillbox.com/) 103 | 104 | ### Team Code Repos 105 | https://github.com/Metronomo-xyz 106 | 107 | ### Team LinkedIn Profiles (if available) 108 | 109 | - [Vladimir Gusev](https://www.linkedin.com/in/gusevv1987/) 110 | - [Yaroslav Bondarchuk](https://www.linkedin.com/in/bondarchukyaroslav/) 111 | - [Vadim Smirnov](https://www.linkedin.com/in/vadim-smirnov-71a66b189/) 112 | 113 | ## Development Status :open_book: 114 | 115 | We are building an infrastructure protocol for creating user growth tools for web3. Currently, we are aiming to develop the first valuable tools, infrastructure, and technology they need. 116 | 117 | We believe MVP will help us provide value for projects in the Mintbase ecosystem and create a foundation for user acquisition infrastructure protocol. 118 | 119 | As for now, we've already done: 120 | 1. [Telegram Bot: @metronomo_bot](https://t.me/metronomo_bot) to test hypotheses on NEARCON and research projects' pains and value requests. We found out that the user acquisition part of the ecosystem lacks the most familiar tools and techniques. 121 | 2. For now, we consider that the primary method to find power users will be RFM-segmentation https://en.wikipedia.org/wiki/RFM_(market_research) 122 | 3. We created basic projects' and users' similarity analysis tools. We found out that it's possible to compute on not very expensive servers and in a reasonable time for creating a product. 123 | 124 | During this project, we are going to get three main results: 125 | - create a module to find power users who interacted with a given smart contract. 126 | - create a module to calculate users similarity measures and find potential power users 127 | - create a module to find a smart-contract which potential power users interact with 128 | 129 | ## Development Roadmap :nut_and_bolt: 130 | 131 | ### Overview 132 | 133 | - **Total Estimated Duration:** 3,5 months 134 | - **Full-Time Equivalent (FTE):** 5 FTE 135 | - **Total Costs:** 25,000 USD 136 | 137 | ### Milestone 1 — Implement power-users search module 138 | 139 | - **Estimated duration:** 1 month 140 | - **FTE:** 0.5 141 | - **Costs:** 2,500 USD 142 | 143 | | Number | Deliverable | Specification | 144 | | -----: | ----------- | ------------- | 145 | | 0a. | License | Apache 2.0 146 | | 0b. | Documentation | We will provide both **inline documentation** of the code and a basic tutorial on deploying and running created module. 147 | | 0c. | Testing Guide | Core functions will be fully covered by unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. | 148 | | 0d. | Docker | We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone. | 149 | | 1. | Power-users-search module | We will create a module that will search for power users of stores build on Mintbase, given the indexed blockchain data in described format. 150 | 151 | - We will create only mapping of Mintbase smart contracts methods and arguments to users engagement model 152 | - We will create users engagement model (to measure user engagement and identify the most valuable users) 153 | 154 | ### Milestone 2 - Implement look-a-like module 155 | 156 | - **Estimated Duration:** 1,5 months 157 | - **FTE:** 1 158 | - **Costs:** 7,500 USD 159 | 160 | | Number | Deliverable | Specification | 161 | | -----: | ----------- | ------------- | 162 | | 0a. | License | proprietary 163 | | 0b. | Documentation | We will provide both **inline documentation** of the code and a basic tutorial on how to deploy and run created module. 164 | | 0c. | Testing Guide | Core functions will be fully covered by unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. | 165 | | 0d. | Docker | We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone. | 166 | | 1. | Look-a-like module | We will create a module that will create a look-a-like (embedded vector) representation of power users in user space. 167 | 168 | - We will create a module that will create a look-a-like (embedded vector) representation of all NEAR users in user space. 169 | - We will implement single frequency-recency engagement evaluation to create user vector representation (however, this method should be quite accurate) 170 | 171 | ### Milestone 3 - Implement the users' similarity module and the users' activity module 172 | 173 | - **Estimated Duration:** 1 month 174 | - **FTE:** 1 175 | - **Costs:** 5,000 USD 176 | 177 | | Number | Deliverable | Specification | 178 | | -----: | ----------- | ------------- | 179 | | 0a. | License | Users similarity module, Similar contracts search module - Apache 2.0. API - poprietary, free for Mintbase ecosystem (proprietary for others) 180 | | 0b. | Documentation | We will provide both **inline documentation** of the code and a basic tutorial on how to deploy and run created module. 181 | | 0c. | Testing Guide | Core functions will be fully covered by unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. | 182 | | 0d. | Docker | We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone. | 183 | | 0e. | Article | We will publish an **article** and perform a workshop explaining how to use created API and receive value from this product. 184 | | 1. | Users similarity module | We will create a module that will find the most similar users in the whole NEAR blockchain given a specific set of look-a-likes 185 | | 2. | Similar contracts search module | We will create a module that will find and count how many potential similar to look-a-like users interacted with each smart contract (with at least one interaction during a given past period) 186 | | 3. | API setup | We will run an API, which Mintbase users or Mintbase itself can use or integrate into Mintbase UI 187 | 188 | ## Future Plans 189 | 190 | In the future, our primary goal is to develop protocol architecture and economics concepts based on user research. 191 | The protocol should allow building tools like (but lot limited to): 192 | - Recommender system for NFT marketplaces 193 | - Personalized user incentives 194 | - Affinity analysis 195 | - Product analytics tools 196 | - Open-source zero-party tracker 197 | - Competitor analysis 198 | - Cohort analysis 199 | - etc. 200 | 201 | Our roadmap includes delivering: 202 | - General power-users analysis module that can be used as a separate open-source product 203 | - Rewrite data extraction module (not covered by this grant application) to user NEAR Lake data (for Google Cloud) instead of NEAR Indexer for Explorer data 204 | - Blend web2 & web3 data to enhance user acquisition 205 | - Provide API to access and manage marketing data 206 | 207 | ## Additional Information :heavy_plus_sign: 208 | 209 | **How did you hear about the Grants Program?** 210 | 211 | from Paul Kuveke at NEARCON 2022 212 | -------------------------------------------------------------------------------- /applications/mintbase-analytics-and-visulization .md: -------------------------------------------------------------------------------- 1 | # Mintbase Grant Proposal 2 | 3 | - **Project Name:** Mintbase Analytics and Visualization Integration 4 | - **Team Name:** DappLooker 5 | - **Payment Address:** dapplooker.near 6 | - **[Level](../README.md#level_slider-levels):** 2 7 | 8 | ## Project Overview :page_facing_up: 9 | 10 | ### Mintbase Analytics and Visualization Integration 11 | 12 | ### Overview 13 | 14 | The Mintbase Analytics and Visualization Integration project is a strategic collaboration between Mintbase and DappLooker, aiming to enrich the user experience for Mintbase creators and team. Our objective is to empower Mintbase Users, Creators, Team, and Mintbase Community with in-depth insights, fostering data-driven decisions and an enhanced overall experience on the platform. 15 | 16 | The proposal involves integrating the GraphQL Indexer of Mintbase with DappLooker, building an ETL (Extract, Transform, Load) system on top of the GraphQL Indexer, and creating comprehensive analytics and visualization tools for Mintbase data, all powered by DappLooker’s intuitive and no-code analytics platform. 17 | 18 | The project will provide the following benefits to the Mintbase community: 19 | 20 | - **Enhanced User Experience:** DappLooker’s analytics and visualization tools integrated with Mintbase offer a more intuitive and user-friendly interface for data access and analysis. 21 | 22 | - **Data-Driven Decisions:** Comprehensive analytics and visualization tools enable users to make informed, data-driven decisions, enriching their overall experience on the platform. 23 | 24 | - **Improved Efficiency:** The ETL system automates data extraction, transformation, and loading from the GraphQL Indexer, enhancing the efficiency of the data analysis process. 25 | 26 | - **Chart/Dashboard Embedding:** DappLooker's APIs tailored for the Mintbase Ecosystem will support embedding Custom Charts, Dashboards, and Visualizations of Mintbase Data for Mintbase Team, Store Owners, and Users. 27 | 28 | ### Project Details 29 | 30 | The proposal outlines a comprehensive no-code Analytics and Visualization Solution tailored for the Mintbase team and Ecosystem. 31 | 32 | - The Integration of Mintbase Ecosystem with DappLooker extends DappLooker’s features, technology, and capabilities to the Mintbase Ecosystem. 33 | 34 | **Data Models/API Specifications:** 35 | 36 | - Integration of Mintbase GraphQL Indexer with DappLooker enables data extraction from Mintbase using APIs. 37 | - ETL system built atop the GraphQL Indexer automates data extraction, transformation, and loading. 38 | - Transformed data is open-source and available on-demand and on DappLooker. 39 | - Charts and Dashboards can be Embedded and Shared openly using published APIs. 40 | 41 | **Technology Stack:** 42 | 43 | - Frontend: AngularJS, Next.js, CSS, HTML 44 | - Backend: Rust, Typescript 45 | - Database: PostgreSQL 46 | 47 | **Documentation:** 48 | 49 | Comprehensive documentation will cover core components, protocols, embedding guide, API endpoints, and user guides for the analytics and visualization tools. 50 | 51 | For reference: 52 | 53 | - [DappLooker Documentation](https://docs.dapplooker.com/) 54 | - [DappLooker SDK on GitHub](https://github.com/dapplooker/dapplooker-sdk) 55 | 56 | **Features:** 57 | 58 | Key features available post-integration: 59 | 60 | - **Browse Mintbase Data:** Explore and navigate Mintbase data in a user-friendly tabular format. 61 | - **Export Data to CSV/Excel:** Ecosystem users can seamlessly export complete data to Excel or CSV files. 62 | - **No-code Queries:** Utilize an intuitive visual editor for querying the Mintbase dataset. Users can query, filter, join, and group data effortlessly. 63 | - **Community Analytics:** Conduct community analytics on the indexed Mintbase dataset. 64 | - **Robust API & Embedding:** Use a highly scalable and robust API SDK to fetch chart data directly onto your platform. Easy embedding of charts and dashboards. 65 | - **Create, Fork, and Edit Charts:** Choose from various visualization types (e.g., line chart, bar chart, pie chart) to create, edit, and fork charts based on the Mintbase data. 66 | - **Create & Share Dashboard:** Build dashboards effortlessly using drag-and-drop functionality and aggregate information from multiple sources into a single dashboard. Share dashboards via URLs and export charts in popular formats like CSV, XLS, and JSON. 67 | - **Collections / Folders:** Organize charts and dashboards using collections. Control visibility and access permissions, making charts/dashboards private or public. 68 | - **Advanced Analytics:** Conduct advanced analytics such as funnel analysis and user retention analysis to monitor active user activity and make informed decisions. 69 | 70 | ### Ecosystem Fit 71 | 72 | Our project seamlessly integrates into Mintbase by enhancing its analytical capabilities, providing valuable insights to the Mintbase Team, Store Owners, and Users. It caters to the need for comprehensive data analytics, empowering users to optimize their stores and make informed decisions, uniquely tailored for the Mintbase/NEAR ecosystem. 73 | 74 | ## Team :busts_in_silhouette: 75 | 76 | ### Team members 77 | 78 | - Co-Founder & CEO: Abhay Singh 79 | - Co-Founder & COO: Abhinav Singh 80 | - CTO: Vikash Choubey 81 | - Head of Growth: Rahul Parmar 82 | - Backend Engineer: Hitesh Kankarwal 83 | - Frontend Engineer: Harsh Rajput 84 | - Frontend Engineer: Aditya Kundurkar 85 | - Full Stack Engineer: Deepak Kashyap 86 | - Full Team: [DappLooker Team](https://dapplooker.com/team) 87 | 88 | ### Contact 89 | 90 | - **Contact Name:** Abhay Singh 91 | - **Contact Email:** abhay@dapplooker.com 92 | - **Website:** https://dapplooker.com/ 93 | 94 | ### Legal Structure 95 | 96 | - **Registered Address:** Flat No 1007, B3 Building, Leisure Town, Hadapsar, Pune, Maharashtra, India - 411028 97 | - **Registered Legal Entity:** DappLooker Solutions PVT LTD 98 | 99 | ### Team's experience 100 | 101 | DappLooker leads the market in providing seamless no-code web3 analytics solutions. Our platform empowers users with analytics for over 15+ networks, and 350+ Dapps with 350M+ data available for analysis. DappLooker is a NEAR Grantee, backed by the NEAR Ecosystem and has onboarded various projects in the NEAR ecosystem, such as MetaPool, Ref Finance, and More. 102 | 103 | Founded in 2021, the DappLooker Team has over 45 years of combined team experience, with 12+ skilled individuals, including Blockchain Engineers, Backend Engineers, Front End Engineers, and a Marketing team, experts in providing the best analytics solutions for Web3. We have successfully collaborated with Near, Polygon, Aave, Moonbeam, and other Ecosystems. 104 | 105 | DappLooker Team: [DappLooker Team](https://dapplooker.com/team) 106 | 107 | ### Team Code Repos 108 | 109 | Organization Github: 110 | - [DappLooker Github](https://github.com/dapplooker) 111 | 112 | Team Github: 113 | - [Abhay Singh Github](https://github.com/abhayait) 114 | - [Abhinav Singh Github](https://github.com/tech-nerd) 115 | - [Vikas Choubey Github](https://github.com/realchoubey) 116 | 117 | ### Team LinkedIn Profiles 118 | - [Abhay Singh LinkedIn](https://www.linkedin.com/in/abhay-singh-15156316/) 119 | - [Abhinav Singh LinkedIn](https://www.linkedin.com/in/reachmeabhinav/) 120 | - [Vikash Choubey LinkedIn](https://www.linkedin.com/in/realchoubey/) 121 | - [Rahul Parmar LinkedIn](https://www.linkedin.com/in/rahulparmar7/) 122 | 123 | ## Development Status :open_book: 124 | 125 | We have conducted preliminary research and discussions related to the project, identifying key components for integration in collaboration with the Mintbase Team. Our team, experienced in developing similar analytics solutions, is well-prepared to leverage DappLookers Technology for Mintbase. 126 | 127 | DappLooker already showcases a comprehensive Near Ecosystem Dashboard: [Near Ecosystem Dashboard](https://dapplooker.com/dashboard/near-ecosystem-dashboard-199) 128 | 129 | ## Development Roadmap :nut_and_bolt: 130 | 131 | The project will go through 2 milestones: 132 | 133 | - Mintbase Integration and No-Code Analytics 134 | - Visualization Tools, Dashboards & APIs 135 | 136 | ### Overview 137 | 138 | - **Total Estimated Duration:** 1 Month 139 | - **Full-Time Equivalent (FTE):** 4 140 | - **Total Costs:** 25,000 USD 141 | 142 | 1. **Mintbase Integration and No-Code Analytics** 143 | - *Estimated Duration:* 2 Weeks 144 | - *FTE:* 2 145 | - *Costs:* 15,000 USD 146 | - **Details of deliverables:** 147 | - Integration of Mintbase GraphQL Indexer 148 | - Building an ETL on top of the GraphQL Indexer 149 | - Making Mintbase Data Available for Custom Analytics & Visualization 150 | 151 | 2. **Visualization Tools, Dashboards & APIs** 152 | - *Estimated Duration:* 2 Weeks 153 | - *FTE:* 2 154 | - *Costs:* 10,000 USD 155 | - **Details of deliverables:** 156 | - Creating Mintbase Store Dashboard 157 | - Creating Mintbase Individual Store Dashboard Template 158 | - Making API SDK & Embedding integration available 159 | - Creating an Interactive Mintbase Cross-Store Comparison dashboard 160 | - Publish Documentation 161 | - Publish API endpoints and embedding links in Documentation 162 | - Co-marketing 163 | 164 | ## Future Plans 165 | 166 | - We plan to continuously enhance and optimize the analytics tools based on user feedback. 167 | - Facilitate creators on Mintbase with additional insights into their stores. 168 | - Ensure store owners can easily share and embed insights. 169 | - Provide the Mintbase team with top-tier analytics solutions. 170 | - Explore collaborations with other NEAR ecosystem projects for a more significant impact and better support for the NEAR Ecosystem. 171 | 172 | ## Additional Information :heavy_plus_sign: 173 | 174 | **How did you hear about the Grants Program?** 175 | We learned about the Grants Program through the Mintbase website and official announcements. 176 | 177 | **Previous Work:** 178 | Our team successfully developed and deployed analytics solutions for various blockchain projects, including Near, Polygon, Aave, and Moonbeam. Our proven track record demonstrates our commitment to delivering high-quality analytics tools for the Web3 space. 179 | 180 | ### Partnerships and Grants: 181 | 182 | We are backed by multiple ecosystems through their ecosystem grants, such as Near, The Graph, Celo, Moonbeam, and more. 183 | 184 | Here is the list of partners that have trusted us: 185 | 186 | - [NEAR Partnership](https://twitter.com/dapplooker/status/1527635695342440448?s=20) Announcement 187 | - [Polygon Dapp Store Kit](https://twitter.com/dapplooker/status/1663975545930149888) Announcement 188 | - [Aave V3 Grant](https://twitter.com/abhayait/status/1571882447377428482?s=20) Announcement 189 | - [Moonbeam Partnership](https://twitter.com/MoonbeamNetwork/status/1519662910301159424?s=20) Announcement 190 | - [BNB Chain Partnership](https://twitter.com/dapplooker/status/1665031299470618626?s=20) Announcement 191 | - [PEAQ Integration](https://twitter.com/dapplooker/status/1629155929345368064?s=20) Announcement 192 | - [Flipside Analytics Partnershipde](https://twitter.com/dapplooker/status/1629155929345368064?s=20) Announcement 193 | - [NFTX Partnership](https://twitter.com/dapplooker/status/1676614625302040578?s=20) Announcement 194 | - [MetricsDAO Partnership](https://twitter.com/dapplooker/status/1651640887888445441?s=20) Announcement 195 | - [Prezenti Grant](https://twitter.com/prezenti_grants/status/1657090707855925248?s=20) Announcement 196 | 197 | Excited to make Mintbase more user-friendly and data-driven, this integration promises efficiency, insights, and improved engagement. Thank you for considering our contribution to Mintbase and Near Ecosystems. -------------------------------------------------------------------------------- /applications/namesky.md: -------------------------------------------------------------------------------- 1 | # Mintbase Grant Proposal 2 | 3 | - **Project Name:** NameSky 4 | - **Team Name:** NameSky Team 5 | - **Payment Address:** liaa.near 6 | - **[Level](../README.md#level_slider-levels):** 1 7 | 8 | ## Project Overview 📄 9 | 10 | NameSky is an NFT project on the NEAR blockchain. It’s built with utilities to make buying & selling NEAR accounts easy and secure. 11 | 12 | ### Overview 13 | 14 | Please provide the following: 15 | 16 | - NameSky is the first marketplace to buy and sell NEAR accounts as NFTs. 17 | - We allow users to trade near accounts (through NFT) on Mintbase. 18 | - Buying & selling a NEAR account is never an easy thing. So we started the NameSky project with a mission to make NEAR account trading easy and secure. 19 | 20 | ### Project Details 21 | 22 | We expect the teams to already have a solid idea about your project's expected final state. Therefore, we ask the teams to submit (where relevant): 23 | 24 | * The current UI and designs are covered in our MVP demo and deployed on the testnet. (links attached below) 25 | * Data models / API specifications of the core functionality 26 | 27 | * NFT Contract: 28 | 29 | * Mint 30 | 31 | > Alice has an account `love.near` and her main account is `alice.near`. Alice turns `love.near` into an NFT owned by `alice.near` through the NameSky app. 32 | > 33 | 34 | - Transfer 35 | 36 | > Alice transfers the NFT `love.near` to her friend Celia (celia.near). 37 | 38 | - Burn 39 | 40 | > Celia burns the NFT `love.near` and gets a **New Seed Phrase** to control account `love.near` again. 41 | > 42 | * NFT Marketplace Contrat: 43 | 44 | - Buy & Sell NFT 45 | - Make an offer & Accept the Offer of NFT 46 | 47 | - Other functionalities: 48 | - Search Near account NFT by account name 49 | - Search user by user name 50 | - Like an NFT 51 | - Notification for NFT buy, sell and offer 52 | 53 | * Technology Stack: 54 | * Smart Contracts: Rust, NEAR SDK, NEAR SYS 55 | * Frontend: React, Typescript, Graphql 56 | * Server: Node.js 57 | * Indexer: The Graph 58 | 59 | * PoC/MVP or other relevant prior work or research on the topic 60 | 61 | * Demo vedio: [https://youtu.be/71JUKrTWSPA](https://youtu.be/71JUKrTWSPA) 62 | * Testnet MVP app: [https://testnet.namesky.app](https://rentverse.netlify.app/) 63 | 64 | ### Ecosystem Fit 65 | 66 | Help us locate your project in the Mintbase landscape and what problems it tries to solve by answering each of these questions: 67 | 68 | Q: Where and how does your project fit into the ecosystem? 69 | In the NEAR blockchain, there is no good way to trade NEAR accounts on a scale. NameSky is solving this problem by leveraging the power of the NFT protocol and making it possible to trade NEAR accounts easily and safely in scale. Also, NameSky is a utility-heavy NFT project that can show the good use case of the NFT protocol. 70 | 71 | 72 | 73 | Q: Who is your target audience (parachain/dapp/wallet/UI developers, designers, your own user base, some dapp's userbase, yourself)? 74 | 75 | 1. First of all, **myself**, **Demo Chen**. I desperately want to have the NEAR account `demo.near` as my identity on the NEAR blockchain, but that account is already registered by someone else. I have no way to even make an offer to him to buy `demo.near`. 76 | 77 | 2. **NEAR account collectors and investors**. It's a proven business both in the web2 and the web3 world. It's very rewarding when you invested early in web domain names or ENS names. 78 | 3. **Founders and Bussiness Owners**. They always want a good NEAR account for people to remember their brand and identity. NameSky is the place for them to find the NEAR accounts they want. 79 | 80 | 81 | 82 | 83 | Q: What need(s) does your project meet? 84 | - NameSky makes it possible to turn a NEAR account into an NFT and vice versa 85 | - NameSky has a dedicated marketplace front to buy/sell NEAR accounts (as NFTs) 86 | - NameSky makes NEAR account sales discoverable through a Twitter bot [NEAR accounts sales bot](https://twitter.com/nearaccountsbot) 87 | 88 | Q: Are there any other projects similar to yours in the Mintbase / NEAR ecosystem? 89 | 90 | There are few prior projects that to trade NEAR accounts, NameSky is the first one that takes advantage of the NFT protocol and also provides an easy-to-use interface to make NEAR account trading approachable, scalable and reliable. 91 | 92 | Similar projects: 93 | - https://gonear.name 94 | - https://nomenmarket.com 95 | - https://nearnames.io 96 | 97 | ## Team 👥 98 | 99 | ### Team members 100 | 101 | - Name of team leader 102 | - Demo Chen 103 | - Names of team members 104 | - Bob Xu 105 | - Coffee 106 | - Clemens 107 | 108 | ### Contact 109 | 110 | - **Contact Name:** Demo Chen 111 | - **Contact Email:** kidliaa@gmail.com 112 | 113 | ### Legal Structure 114 | 115 | We don't have a formally registered company at the moment. 116 | 117 | ### Team's experience 118 | 119 | - **Demo Chen**, product and frontend developer. 10 years of experience in web development and loves building things. The founding team of workstream.us. 120 | - **Bob Xu**, contract developer. A big fan of NEAR since early 2021, and an active member in the NEAR ecosystem. 5 years of experience in backend development and 1.5 years experience of in NEAR contract development. 121 | - **Coffee**, contract developer. Familiar with the NEAR ecosystem and active in the NEAR community. 122 | - **Clemens**, product designer. https://clemensmorris.com 123 | 124 | 125 | ### Team Code Repos 126 | 127 | - https://github.com/nameskyteam 128 | 129 | Please also provide the GitHub accounts of all team members. If they contain no activity, references to projects hosted elsewhere or live are also fine. 130 | 131 | - https://github.com/hsxyl 132 | - https://github.com/hash0000ff 133 | - https://github.com/hanakannzashi 134 | 135 | 136 | ### Team LinkedIn Profiles (if available) 137 | 138 | - https://www.linkedin.com/in/liang-chen-3b5855132/ 139 | 140 | ## Development Status 📖 141 | 142 | 143 | - GitHub repos (we now in private mode, let us know to add you as a member): https://github.com/nameskyteam 144 | - testnet MVP version: https://testnet.namesky.app 145 | - Near account NFT sales bot: https://twitter.com/nearaccountsbot 146 | - previous interface iterations, such as mock-ups and wireframes. [Figma design link](https://www.figma.com/file/3PgMxMQmsttOdccg32H7bq/NameSky?node-id=22759%3A2639&t=ceAaZHDHZeKUM70n-0) 147 | 148 | ## Development Roadmap 🔩 149 | 150 | ### Overview 151 | 152 | - **Total Estimated Duration:** 6 months 153 | - **Full-Time Equivalent (FTE):** 3 FTE 154 | - **Total Costs:** 20,000 USD 155 | 156 | ### Milestone 1 — Audit 157 | 158 | - **Costs:** 20,000 USD 159 | - We have contacted some security companies, and they have feedback us about their price: 160 | - BlockSec: ~80,000 USD 161 | - Pessimistic Security: ~30,000 USD 162 | 163 | ## Future Plans 164 | 165 | - At the moment, our first priority is to apply funds for auditing our Near contracts then we can go mainnet. 166 | - In the long term, We will collaborate with other NFT projects on NEAR to integrate near account NFT in their project. And we'll keep optimizing and developing new features based on user feedback. 167 | 168 | ## Additional Information ➕ 169 | 170 | **How did you hear about the Grants Program?** Announcement by another team 171 | 172 | Here you can also add any additional information that you think is relevant to this application but isn't part of it already, such as: 173 | 174 | - Work you have already done. 175 | 176 | > We have finished Milestone 1. 177 | 178 | - If any other teams have already contributed (financially) to the project. 179 | 180 | > No. 181 | 182 | - Previous grants you may have applied for. 183 | 184 | > We haven't applied for funds. 185 | 186 | -------------------------------------------------------------------------------- /applications/puzzletask_license_nft.md: -------------------------------------------------------------------------------- 1 | # Mintbase Grant Proposal 2 | 3 | 4 | 5 | - **Project Name:** Puzzletask NFT Client Certification 6 | - **Team Name:** Puzzletask 7 | - **Payment Address:** puzzletask.near 8 | - **[Level](../README.md#level_slider-levels):** 2 9 | 10 | 11 | ## Project Overview 12 | 13 | 14 | Please provide the following: 15 | 16 | Puzzletask - Blockchain Client Certification 17 | - Client NFT Certification 18 | - A brief description of your project. 19 | - Puzzletask is a no-code platform for Food Safety and Traceability Management serving Hospitality and Food Retail Sectors towards supply chain optimization. We cater to suppliers, hotels, retailers, and end consumers to encourage interaction in a data exchange micro-economy that incentivizes the sharing of valuable data to optimize the supply chain. Our solution has two revenue streams, one based on a SaaS Module and the other based on a Data Monetizing module. 20 | In orther to slowly bring Blockchain technology for such a traditional sector as Food retail and Hospitality, we are launching our NFT Certificate to highlight the customers that are getting into the digital transformation path. This certification approach, from customer certification to license management, can be used in many ways in our business model. The solution will be based on the implementation of an ERP connected NFT Minter that will be available for the community in a form of a library. 21 | 22 | - An indication of how your project relates to / integrates into the Mintbase / NEAR ecosystem. 23 | - We are bringing a real life use case for NFTs as a way to certify our customers and provide them with a simple first contact with blockchain and NEAR wallet. 24 | - An indication of why your team is interested in creating this project. 25 | - We aim to highlight the customers that are buying our tool for food safety and traceability management. 26 | 27 | ### Project Details 28 | 29 | We expect the teams to already have a solid idea about your project's expected final state. Therefore, we ask the teams to submit (where relevant): 30 | 31 | - [Mockups/designs of any UI components](https://www.figma.com/proto/LQa40vQvo3WsaHbvMzAXK1/Puzzletask-NFT-certification?node-id=3%3A12&scaling=min-zoom&page-id=0%3A1&starting-point-node-id=3%3A12) 32 | - Data models / API specifications of the core functionality: 33 | - We propose to develop a javascript library based on MintbaseJS and an extended version of NEP-171 that will be used to mint, transfer and burn an NFT with a set of attributes dependant on third party authorization. This authorizations will be granted by an external API via an Oracle. 34 | 35 | - After this project implementation, the library will be used by the Puzzletask SaaS to mint a certificate with a set of relevant attributes according to the permissions set by Puzzletask. The transferability of the NFT will also be authorized by Puzzletask API according to the target wallet address defined by the user. NFT Burn function will be available to the owner and won't be dependant on any Puzzletask permission. 36 | 37 | - After this first project, there will be a set of pages in Puzzletask SaaS certificate workflow that will use this library to mint, transfer and burn for the owner. There will be a public page for NFT existence verification and consequent data retrieval. 38 | 39 | - An overview of the technology stack to be used: 40 | - Javascript; 41 | - React; 42 | - MintbaseJS; 43 | - near-sdk-rs 44 | 45 | ### Ecosystem Fit 46 | 47 | Help us locate your project in the Mintbase landscape and what problems it tries to solve by answering each of these questions: 48 | 49 | - Where and how does your project fit into the ecosystem? 50 | - The project is kind of a new category among the NFT's and we defined has a Business Utility NFT - Under Puzzletask context, after this project implementation, we will develop and provide a first interaction with blockchain for businesses in the food industry. By implementing our project on this kind of market players we will allow them to start to accept NEAR because it will be mandatory to create a wallet to mint and manage the NFT; 51 | - Who is your target audience (parachain/dapp/wallet/UI developers, designers, your own user base, some dapp's userbase, yourself)? 52 | - Food Operators such as hotels, retailers and restaurants. We are planning to implement a feedback solution with consumers in a later version of these project. 53 | - What need(s) does your project meet? 54 | - NFT Certification to promote the companies that are reducing their food waste and paper by using our digital food safety and traceability tool. 55 | - Are there any other projects similar to yours in the Mintbase / NEAR ecosystem? 56 | - There isn't a similar project on NEAR Protocol targeting the Supply Chain Sector and even considering other ecosystems, there is a lack of tradicional business adoption and this could a great oportunity for Mintbase and Near to leverage their market positioning. Puzzletask will be a Supply Chain Optimization company and already have a fully functional SaaS for hotels and food retailers. 57 | 58 | ## Team 59 | 60 | ### Team members 61 | 62 | - Adalberto Rodrigues 63 | - Pedro Rodrigues 64 | - Sandro Leitão 65 | - Vicente Almeida 66 | - Esfandiar Lagevardi 67 | 68 | ### Contact 69 | 70 | - **Contact Name:** Adalberto Rodrigues 71 | - **Contact Email:** arodrigues@puzzletask.com 72 | - **Website:** https://puzzletask.com 73 | 74 | ### Legal Structure 75 | 76 | - **Registered Address:** Rua António Alçada Batista, nº2, Bloco A, 5ºa, Lisboa 77 | - **Registered Legal Entity:** 78 | 79 | ### Team's experience 80 | 81 | Please describe the team's relevant experience. If your project involves development work, we would appreciate it if you singled out a few interesting projects or contributions made by team members in the past. For research-related grants, references to past publications and projects in a related domain are helpful. 82 | 83 | If anyone on your team has applied for a grant at the Mintbase previously, please list the name of the project and legal entity here. 84 | 85 | In terms of technical knowledge the team doesn't have experience in RUST or Solidity but that demonstrates the capabilities to successfully create, develop, deploy and maintain applications with sustainable business models. 86 | 87 | The development team accumulates experience in Backend and Frontend Development, Systems and Data Architecture, DevOps and SRE. 88 | It has been leading software development and maintenance in portuguese top companies and projects always using the best practices in the industry. We may highlight SAPO Adwords that served millions of ads requests per day, MEO Cloud - Altice Labs that served petabyte scale data to near half a million users, the foundation and launch of Advertio's technical team, processes, software and infrastructure and BPstat - Banco de Portugal's statistical portal that manages millions of time series that are explorable by the public via an extensive set of tools and related content. 89 | 90 | On the project/ product management and tokenomics, the team presents a senior level regarding the capability to create a product from 0 to scale with 10 years of experience in tech projects as well as arround 8 years in tokenomics desing, treasury manament strategies and security audits. 91 | 92 | 93 | ### Team Code Repos 94 | 95 | 96 | Please also provide the GitHub accounts of all team members. If they contain no activity, references to projects hosted elsewhere or live are also fine. 97 | 98 | - https://github.com/car3ca 99 | - https://github.com/vice2al 100 | 101 | ### Team LinkedIn Profiles (if available) 102 | 103 | - https://www.linkedin.com/in/adalbertorodrigues/ 104 | - https://www.linkedin.com/in/pgr42/ 105 | - https://www.linkedin.com/in/vicente-moitinho-de-almeida/ 106 | - https://www.linkedin.com/in/sandro-leitao/ 107 | - https://www.linkedin.com/in/esfandiar-benjamin-lagevardi-9b631086/ 108 | 109 | 110 | 111 | ## Development Status 112 | 113 | 114 | ### Overview 115 | 116 | - **Total Estimated Duration:** 5 months 117 | - **Full-Time Equivalent (FTE):** 1,5 (Team of 5 members) 118 | - **Total Costs:** 20.000 USD 119 | 120 | ### Milestone 1 — User session connected NFT minter library development 121 | 122 | - **Estimated duration:** 3 months 123 | - **FTE:** 1,5 124 | - **Costs:** 12.000 USD 125 | 126 | | Number | Deliverable | Specification | 127 | | -----: | ----------- | ------------- | 128 | | 0a. | License | Apache 2.0 / GPLv3 / MIT / Unlicense | 129 | | 0b. | Testing Guide | Core functions will be fully covered by unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. | 130 | | 1. | Mintbase module: User session connected NFT minter library | We will create a Mintbase / NEAR module that will able developers to use a NFT for certifications on Near Blockchain. The library will be developed in javascript based on MintbaseJS that will be used to mint, manage and subsequently retrieve an NFT with a set of attributes for a connected wallet. This will be a beta version. | 131 | 132 | 133 | 134 | ### Milestone 2 — Library final version 135 | 136 | - **Estimated Duration:** 2 month 137 | - **FTE:** 1,5 138 | - **Costs:** 8.000 USD 139 | 140 | 141 | 142 | | Number | Deliverable | Specification | 143 | | -----: | ----------- | ------------- | 144 | | 0a. | Testing Guide | Core functions will be fully covered by unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. | 145 | | 0b. | Documentation | We will provide general library usage documentation. | 146 | | 1. | Documentation for library integration | We will write documentation with an example of this library integration. This example will try to demonstrate a real use case with the following features / workflow: client authentication and wallet connection to mint, transfer and burn a certificate dependant on third party authorization; | 147 | | 2. | NEAR chain integration | The Module will interact with the Near Wallet and chain.| 148 | | 3. | Mintbase Module: User session connected NFT Minter library final version| We will create the final version of the library.| 149 | 150 | 151 | 152 | 153 | ## Future Plans 154 | 155 | Please include here 156 | 157 | - how you intend to use, enhance, promote and support your project in the short term, and the team's long-term plans and intentions in relation to it. 158 | 159 | We will integrate the library into the Puzzletask SaaS. After the client authentication and after wallet connection to mint a certificate with a set of relevant attributes. There will be a set of pages in Puzzletask SaaS certificate workflow that will use this library to mint, transfer and burn for the owner. There will be a public page for NFT existence verification and consequent data retrieval. 160 | 161 | By implementing this project we open the possibility to allow hotels to start to receive payments using $NEAR. This first approach will be important to start to educate our customer base about blockchain. This fact is crucial to allow our migration for a business model based on a data monetization in a micro-economy that incentivizes the sharing of valuable data to optimize the supply chain. 162 | 163 | ## Additional Information 164 | 165 | **How did you hear about the Grants Program?** 166 | 167 | Personal recommendation (Oscar Andrade) 168 | 169 | **Here you can also add any additional information that you think is relevant to this application but isn't part of it already, such as:** 170 | 171 | - We developed a fully functional SaaS for food safety and traceability digitalization used by brands such as Four Seasons Fairways, Mother Burguer, Quiosques de Lisboa and Intermarché. 172 | -------------------------------------------------------------------------------- /applications/the_everything_project.md: -------------------------------------------------------------------------------- 1 | # Mintbase Grant Proposal 2 | 3 | - **Project Name:** the **everything** project 4 | - **Team Name:** everything labs 5 | - **Payment Address:** evrything.near (notice the missing e) 6 | - **Level:** 1 7 | 8 | 9 | ## Project Overview :page_facing_up: 10 | 11 | ### Overview 12 | 13 | the **everything** project, centralizing data for the circular economy. 14 | 15 | Inconveniences and inefficiencies in secondary product markets are creating wasteful consumer habits and stifling innovation in addressing the climate crisis. The solution is to centralize product data online and to create open source white-label applications, marketplaces, and services that can be adapted and serve as the foundation for an interconnected circular economy. 16 | Check out this diagram [here](https://about.everything.dev/diagram) to see what this looks like. 17 | 18 | Through the **everything** app or any of its derivatives, users can upload "Things" and, when marked public or available for sale, these Things will be minted on chain in order to handle transactions and to maintain a history of ownership. 19 | Then, minted things become available on the **everything** marketplace or any of its derivatives, where users can buy, sell, trade, or transfer their real, tangible assets. 20 | 21 | 22 | ### Project Details 23 | 24 | - An overview of the project and it's technical architecture: [Link](https://about.everything.dev/diagram) 25 | - An amatuer Figma of the **everything** app: [Link](https://www.figma.com/file/8cL2PwMBPPj2voOOMu54y9/everything-app-v1) 26 | - The original POC submitted to NEAR Megabuild: [Link](https://devpost.com/software/near-frontier) 27 | - A video showing v0 of the **everything** app: [Link](https://www.instagram.com/reel/ChA8Ic0NaRb/?igshid=ZjA0NjI3M2I=) 28 | 29 | 30 | **NOTE**: 31 | 32 | While fraud and item illegitimacy are real issues when pairing NFTs with real, tangible assets, we need to consider that this project is focusing on secondhand and common products, not luxury goods. 33 | Of course there will be some level of protection, but this is a risk that the user needs to acknowledge and the product is not exactly trying to solve. 34 | Eventually, some sort of distribution network (grass-roots supply chain) could serve as an oracle for verifying things. 35 | 36 | ### Ecosystem Fit 37 | 38 | A [recent study](https://newsroom.thredup.com/news/thredup-releases-10th-annual-resale-report-with-insights-on-a-decade-of-resale) suggests that the secondhand product market has become a global phenomenon and is estimated to more than double by 2026, reaching $82 billion — 3X faster than the global apparel market overall. 39 | However, it is also a very unorganized and disjointed product market: current solutions are not prepared for the mass onboarding of every day objects onto the internet. 40 | 1) Thrift stores and small businesses want effective ways to move inventory online without having to maintain listings across multiple different marketplaces. As opposed to Shopify, with everything, they can upload their products and have them not only featured on their own branded site, but automatically listed on the **everything** marketplace. 41 | 2) Consumers want a central place where they can search for a product and find the closest and best match, without having to visit multiple marketplaces or visit multiple physical locations. 42 | 3) Recycling services want their inflows to be sorted prior to arrival in order to keep down costs. 43 | 4) Recycling services want to secure buyers for the recycled materials and consumers want confidence in the sustainability of the products they're buying (the closed loop forming the circular economy). 44 | 45 | All of these opportunities need a foundation to build on so things only need to be uploaded once and then can be queried by the many applications, marketplaces, and services individually. 46 | 47 | With that said, the **everything** app (and its white-label implementation) features a streamlined process for uploading real, tangible things online. 48 | The white label implementation can be adapted by anybody for any reason in order to create a personalized application and this application could also need a specific streamlined process for uploading things online. 49 | 50 | As long as these applications use the **everything** SDK to upload their things online (which is a necessity for the Thing to be added to the inventory of everything), then Mintbase will be the solution for minting. 51 | 52 | - Are there any other projects similar to yours in the Mintbase / NEAR ecosystem? 53 | 54 | Outside of the Mintbase/ NEAR ecosystem, there are other projects that are attempting to tokenize real, tangible assets such as [4K Marketplace](https://4k.com/press), but they all focus on real estate or luxury items. 55 | There are also off-chain solutions like [Digimarc](https://www.digimarc.com), but they focus on new products straight from production. 56 | 57 | Nobody in any ecosystem is tokenizing common everyday and secondhand items. 58 | 59 | ## Team :busts_in_silhouette: 60 | 61 | ### Team members 62 | 63 | Project Lead and Developer: Elliot Braem 64 | 65 | Marketing & PR: Danielle Dvorchak 66 | 67 | Accounting & Junior Developer: Bobby Rein 68 | 69 | Also associated with design studio [Akaer.Studio](https://www.akaer.studio) for business development, graphic design, and more. 70 | 71 | 72 | ### Contact 73 | 74 | - **Contact Name:** Elliot Braem 75 | - **Contact Email:** elliot@everything.dev 76 | - **Website:** [about.everything.dev](https://about.everything.dev) 77 | 78 | ### Legal Structure 79 | 80 | - **Registered Address:** 16192 Coastal Highway, Lewes, Delaware 19958 USA 81 | - **Registered Legal Entity:** everything labs LLC 82 | 83 | ### Team's experience 84 | 85 | For three years, I designed, developed, and scaled critical applications for a large asset management bank's fund accounting. 86 | I've been exploring technologies and building out several proof of concepts for **everything** for the better part of the year. 87 | The team is based in Brooklyn and has connections to thrift stores, fashion activist organizations, and secondary market organizations in NYC. 88 | 89 | 90 | 91 | ### Team Code Repos 92 | 93 | - https://github.com/near-everything 94 | - https://github.com/near-everything/app (building new mobile app out on feature/native-app branch) 95 | - https://github.com/near-everything/marketplace 96 | - https://github.com/near-everything/dashboard 97 | 98 | (currently have the api private) 99 | 100 | (subgraph and smart contracts repos exist, but this would be replaced with Mintbase) 101 | 102 | Please also provide the GitHub accounts of all team members. If they contain no activity, references to projects hosted elsewhere or live are also fine. 103 | 104 | - https://github.com/elliotBraem 105 | 106 | ### Team LinkedIn Profiles (if available) 107 | 108 | - https://www.linkedin.com/in/elliot-braem/ 109 | 110 | 111 | ## Development Status :open_book: 112 | 113 | This project has been an effort since the beginning of the year, starting with [this submission](https://devpost.com/software/near-frontier) into NEAR Megabuild. It has gone through several prototypes and redesigns while the idea has been explored and fine-tuned. 114 | An example of a redesign is [v0](https://www.instagram.com/reel/ChA8Ic0NaRb/?igshid=ZjA0NjI3M2I=) of the everything app which was integrated with NEAR and had a POC marketplace querying from the subgraph. 115 | 116 | The team is now building v1-beta of the everything app following the adjustments that have been made since v0. 117 | 118 | Follow the progress on [Tik Tok](https://www.tiktok.com/@everything.project?lang=en) or [Instagram](https://www.instagram.com/evrythingprject/?hl=en). 119 | 120 | 121 | ## Development Roadmap :nut_and_bolt: 122 | 123 | ### Overview 124 | 125 | - **Total Estimated Duration:** 2 months 126 | - **Full-Time Equivalent (FTE):** 1.5 (will be actively recruiting contribitors) 127 | - **Total Costs:** 10,000 USD 128 | 129 | ### Milestone 1 — SDK Development 130 | 131 | - **Estimated duration:** 1 month 132 | - **FTE:** 1.5 (will be actively recruiting contribitors) 133 | - **Costs:** 6,000 USD 134 | 135 | | Number | Deliverable | Specification | 136 | | -----: | ----------- | ------------- | 137 | | 0a. | License | MIT | 138 | | 0b. | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how a developer can use the SDK in their own application to mint "things", pull public data from the indexer api, and request additional details from the express api. | 139 | | 0c. | Testing Guide | Core functions will be fully covered by unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. | 140 | | 0d. | Docker | We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone. | 141 | | 1. | SDK Development: Creating Things | We will build functionality that allows developers to use our SDK to create Things in the off-chain database and mint records of these using Mintbase (if marked public) | 142 | | 2. | SDK Development: Saving media | We will build functionality that uploads media to a distributed file system (IPFS) | 143 | | 3. | SDK Development: Reading private data | We will build functionality that enables developers to read private data from the off chain database | 144 | 145 | ### Milestone 2 Example — SDK Integration with the everything app 146 | 147 | - **Estimated duration:** 1 month 148 | - **FTE:** 1.5 (will be actively recruiting contribitors) 149 | - **Costs:** 4,000 USD 150 | 151 | | Number | Deliverable | Specification | 152 | | -----: | ----------- | ------------- | 153 | | 0a. | License | MIT | 154 | | 0b. | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how a developer can clone and adapt the **everything** app for their own specific purpose. | 155 | | 0c. | Testing Guide | Core functions of the app will be fully covered by unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. | 156 | | 0d. | Docker | We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone. | 157 | | 1. | UI Design | We will hire a product designer to design the core functionalities of the everything app: User can onboard a Thing, User can upload Media, User can view their Things, User can view other user's public things. (ideally this would start during milestone 1) | 158 | | 2. | Figma Template | We will provide a Figma template that can be adapted to any purpose relevant to the **everything** app. | 159 | | 1. | SDK Integration: Creating Things | We will integrate the **everything** SDK into the Thing onboarding functionality. Users can mark a Thing to be public or private. Public things are minted on chain via Mintbase, private things are not. | 160 | | 2. | SDK Integration: Saving media | We will integrate the **everything** SDK into the media upload functionality during creation of a Thing. Media will be stored on a distributed file system. | 161 | | 3. | SDK Integration: Reading private data | We will integrate the **everything** SDK into the users profile so they can read their private data using their access token from the identity provider. Other users will not be able to access this data. | 162 | | 4. | Full UI Integration | All SDK developments above have been developed to the **everything** app. Users will be able to create things privately and publicly via the app. If private, then the thing will be saved off-chain only, and if public, then the thing will be saved off-chain as well as minted via Mintbase. Users will be able to upload media attached to these things and this Media will be stored in a distributed file system via the SDK. Users will be able to see their privately uploaded things on their profile. | 163 | 164 | ... 165 | ## Future Plans 166 | 167 | I do daily standups on [Tik Tok](https://www.tiktok.com/@everything.project?lang=en) and [Instagram](https://www.instagram.com/evrythingprject/?hl=en) and will be producing other videos as well. Through these channels I hope to gain support and recruit contributors. 168 | 169 | For long term plans, see the [current roadmap](https://about.everything.dev/roadmap). 170 | 171 | 172 | 173 | ## Additional Information :heavy_plus_sign: 174 | 175 | **How did you hear about the Grants Program?** Attended "Creating business models with NFTs" presented by Mintbase COO Paul Kuveke, hosted by EmpireDAO. 176 | 177 | I found out about this grant program yesterday and have rushed to put together this proposal all last night and today. Please mind any shortcomings although I tried to be as thorough as possible. Thank you for considering my application and please let me know if there is any more information needed. 178 | -------------------------------------------------------------------------------- /applications/zettablock.md: -------------------------------------------------------------------------------- 1 | # Mintbase Grant Proposal 2 | 3 | > This document will be part of the terms and conditions of your agreement and therefore needs to contain all the required information about the project. Don't remove any of the mandatory parts presented in bold letters or as headlines. Blockquote sections starting with a `>` (such as this one) can be removed. 4 | > 5 | > See the [Grants Program Process](https://github.com/Mintbase/Grants-Program/#pencil-process) on how to submit a proposal. 6 | 7 | - **Project Name:** ZettaBlock 8 | - **Team Name:** DataLego Inc. 9 | - **Payment Address:** bca49fc67774e519ae8d70f572c08ecb5a63d8f55ad837da64963bbd4634c43c 10 | - **[Level](../README.md#level_slider-levels):** 2 11 | 12 | > ⚠️ *The combination of your GitHub account submitting the application and the payment address above will be your unique identifier during the program. Please keep them safe.* 13 | 14 | ## Project Overview :page_facing_up: 15 | 16 | If this application is in response to an RFP, please indicate this on the first line of this section. 17 | 18 | If this is an application for a follow-up grant (the continuation of an earlier, successful Mintbase grant), please provide name and/or pull request of said grant on the first line of this section. 19 | 20 | ### Overview 21 | 22 | Project Name: ZettaBlock NEAR Integration 23 | Tagline: "Empowering NEAR Developers with Advanced Data Infrastructure and Custom API Solutions." 24 | 25 | 26 | ### Project Details 27 | 28 | **Description**: ZettaBlock NEAR Integration is a pioneering project aimed at integrating the NEAR blockchain into the ZettaBlock platform. This integration will provide the NEAR developer ecosystem with access to a comprehensive full-stack data infrastructure, complete with custom API capabilities. Our project focuses on designing and implementing data models specifically for NEAR, establishing a data lake ingestion pipeline with a robust data quality framework, and developing a suite of custom GraphQL APIs. This initiative will significantly enhance the efficiency and capabilities of NEAR developers, enabling them to access, analyze, and utilize blockchain data more effectively for a variety of innovative applications. 29 | 30 | 31 | ##### Relation to / Integration into the Mintbase / NEAR Ecosystem 32 | 33 | 34 | **Integration**: Our project is directly aligned with the Mintbase and NEAR ecosystems, as it provides essential infrastructure and tools that NEAR developers require. By integrating NEAR blockchain data into ZettaBlock's platform, we are creating a bridge that connects NEAR's blockchain capabilities with advanced data management and API services. This integration will facilitate a more dynamic and efficient development environment within the Mintbase ecosystem, enabling developers to build more sophisticated and scalable applications on the NEAR blockchain. 35 | 36 | 37 | ##### Reason for Team's Interest in the Project: 38 | 39 | **Team's Interest**: Our team is deeply committed to advancing blockchain technology and its applications. We recognize the potential of the NEAR blockchain and its growing ecosystem. By contributing to this space, we aim to address the challenges faced by developers in managing and utilizing blockchain data. Our interest lies in leveraging our expertise in data infrastructure to enhance the capabilities of NEAR developers, thereby fostering innovation and growth within the Mintbase and NEAR communities. This project aligns with our vision of making blockchain data more accessible and useful, ultimately contributing to the broader development and adoption of blockchain technology. 40 | 41 | 42 | ### Project Fit in the Ecosystem 43 | 44 | 45 | ##### Where and how does your project fit into the ecosystem? 46 | 47 | ZettaBlock's integration with the NEAR blockchain aligns seamlessly with the Mintbase ecosystem. By providing full-stack data infrastructure and custom API capabilities to the NEAR developer community, our project enhances the accessibility and utility of blockchain data. This integration facilitates a more robust and dynamic environment for developers, enabling them to build more efficient and innovative applications on the NEAR platform. 48 | 49 | ##### Who is your target audience? 50 | 51 | Our primary target audience includes blockchain developers, particularly those working within the NEAR ecosystem. This encompasses developers of decentralized applications (dApps), blockchain infrastructure specialists, and data analysts who require comprehensive and reliable blockchain data for their projects. Additionally, our services cater to the broader NEAR community, including wallet and UI developers, who can leverage our data models and APIs for enhanced functionality. 52 | 53 | ##### What need(s) does your project meet? 54 | 55 | Our project addresses the critical need for robust, scalable, and easily accessible blockchain data solutions. By integrating NEAR blockchain data into ZettaBlock's platform, we provide developers with powerful tools to access, analyze, and utilize blockchain data more effectively. This includes custom GraphQL API suites and enhanced pre-built APIs, which streamline data handling and improve the overall efficiency of blockchain-based projects. 56 | 57 | ##### Are there any similar projects in the Mintbase / NEAR ecosystem? 58 | 59 | While there are projects that offer blockchain data solutions, ZettaBlock's approach is unique in its comprehensive integration with the NEAR blockchain and its focus on full-stack data infrastructure. Our custom API capabilities and emphasis on data quality frameworks set us apart, offering a more tailored and efficient solution for NEAR developers. 60 | 61 | ##### If not, are there similar projects in related ecosystems? 62 | 63 | Similar projects exist in other blockchain ecosystems, but they often lack the specific focus and customization that ZettaBlock offers for the NEAR ecosystem. Our project is distinct in its deep integration with NEAR and its commitment to providing a full suite of data services specifically designed for this blockchain. 64 | 65 | ### Ecosystem Fit 66 | 67 | ##### How does your project contribute to the Mintbase landscape? 68 | 69 | ZettaBlock's project contributes to the Mintbase landscape by enhancing the data infrastructure available to NEAR developers. This not only empowers current developers within the ecosystem but also attracts new talent and projects, thereby enriching the Mintbase community with a wider range of applications and use cases. 70 | 71 | 72 | ##### Problem Solving: 73 | 74 | Our project solves the problem of fragmented and inefficient access to blockchain data. By offering a centralized, high-quality data solution, we enable developers to focus more on innovation and less on the complexities of data management. This leads to the creation of more sophisticated and user-friendly dApps, ultimately benefiting the entire Mintbase and NEAR ecosystem. 75 | 76 | ##### Conclusion 77 | 78 | In summary, ZettaBlock's integration with the NEAR blockchain represents a significant advancement in blockchain data infrastructure. Our project not only meets a vital need within the Mintbase ecosystem but also sets a new standard for data accessibility and utility, paving the way for more innovative and efficient blockchain development. 79 | 80 | 81 | ## Team :busts_in_silhouette: 82 | 83 | ### Team members 84 | 85 | - Name of team leader: @KonScanner 86 | - Names of team members: @springzh, @ken-gu, @taotaome 87 | 88 | ### Contact 89 | 90 | - **Contact Name:** Jordan Davis 91 | - **Contact Email:** jordan.davis@zettablock.com 92 | - **Website:** www.zettablock.com 93 | 94 | ### Legal Structure 95 | 96 | - **Registered Address:** 16 N San Mateo Dr, San Mateo, CA 94401 97 | - **Registered Legal Entity:** DataLego, Inc 98 | 99 | ### Team's experience 100 | 101 | A cross-functional team of seasoned professionals with extensive experience in data infra, ML, Blockchain, R&D, product, and growth, who have built data infra solutions at Databricks, Uber, Confluent, Meta, Polygon, Binance, and other top companies before. 102 | 103 | If anyone on your team has applied for a grant at the Mintbase previously, please list the name of the project and legal entity here. 104 | 105 | N/A 106 | 107 | ### Team Code Repos 108 | Most repositories (95%+) are private, find some public ones listed below 109 | - https://github.com/Zettablock/zetta-dbt-action 110 | - https://github.com/Zettablock/trino-public 111 | 112 | ### Team LinkedIn Profiles (if available) 113 | - https://www.linkedin.com/company/zettablockhq/ 114 | 115 | ### Overview & Roadmap 116 | Integrate NEAR blockchain into the ZettaBlock platform to provide NEAR developer ecosystem access to full-stack data infrastructure with custom API capabilities. 117 | - **Total Estimated Duration:** 1 month, 2 weeks 118 | - **Full-Time Equivalent (FTE):** 5 119 | - **Total Costs:** 25,000 USD 120 | 121 | ### Milestone 1 - Design and Implement Data Models for Near 122 | Investigate competitor landscape, crawl test data from node, design final tables based on the understanding of exercise. 123 | - **Estimated duration:** 2 weeks 124 | - **FTE:** 2 125 | - **Costs:** 5,000 USD 126 | 127 | ### Milestone 2 - Data Lake Ingestion pipeline, with data quality framework and tests 128 | Implement end-to-end ingestion framework for Near blockchain, from crawler component to data quality assuring components as well as a testing framework. 129 | - **Estimated Duration:** 1 month 130 | - **FTE:** 3 131 | - **Costs:** 20,000 USD 132 | 133 | ## Future Plans 134 | 135 | - Finalize backfilling of Near into Data Lake 136 | - Create Near real-time ingestor + data quality framework 137 | - Custom GraphQL API suite 138 | - Enhanced pre-built APIs (token metadata, balances, dex swaps, NFT sales, e.t.c) 139 | - Next Gen Near explorer* 140 | 141 | 142 | ## Additional Information :heavy_plus_sign: 143 | 144 | **How did you hear about the Grants Program?** Personal recommendation 145 | 146 | Here you can also add any additional information that you think is relevant to this application but isn't part of it already, such as: 147 | 148 | [docs.zettablock.com](https://docs.zettablock.com/) 149 | [blog.zettablock.com](https://blog.zettablock.com) 150 | -------------------------------------------------------------------------------- /docs/accepted_grant_applications.md: -------------------------------------------------------------------------------- 1 | # Accepted Grant Applications 2 | 3 | > **:loudspeaker:** This page will provide an overview of accepted grant applications. 4 | -------------------------------------------------------------------------------- /docs/announcement-guidelines.md: -------------------------------------------------------------------------------- 1 | # Announcement Guidelines 2 | 3 | > Guidelines updated April 2022 4 | 5 | Mintbase supports many teams and organizations throughout the ecosystem. We often receive requests to participate in project announcements. Unfortunately, due to the high volume of requests, we rarely do joint announcements and do not provide quotes. 6 | 7 | In the context of the grants programs, we ask teams not to make any announcements before **the first milestone has been accepted**. This is in order to protect the community from projects that only intend to use the grant announcement to raise funds and/or interest but don't intend to deliver on the application, which has unfortunately happened in the past. For this reason, we reserve the right to terminate grants if this rule is not observed. 8 | 9 | Once you have completed your milestone, we can help by reviewing and proofreading your announcement. When you have drafted your announcement send it to [grants@mintbase.io](mailto:grants@mintbase.io). Please allow 1-3 working days where possible for proofreading articles and wait until the milestone has been accepted to publish it. 10 | 11 | We also cross-promote the most recent projects and their milestones on Twitter on the second Monday of every month, so please keep us updated and send us the links to your published tweets regarding your announcements. 12 | 13 | ## We recommend the following guidelines when writing your post 14 | 15 | - The post should be strategic in nature, focusing on the tech rather than the "announcement" element. 16 | - The team should point to the work, in order to attract attention for the project and demonstrate momentum in the ecosystem. It should be informative for builders and the larger community. 17 | - The post should include a link to a GitHub repository or elsewhere to showcase what's been built so far. 18 | - Suggested flow for the post: 19 | - This is what the team has built so far. 20 | - These are the team's future development plans. 21 | - This is how the technology will contribute to the Mintbase ecosystem. 22 | 23 | ## Key components 24 | 25 | 1. A blog post header image 26 | - An image helps when sharing the announcement on social networks. It's more prominent in feeds and looks more professional. 27 | - Image ideas include showing how Mintbase or Mintbase fit into your flow. Or you can simply put the teams' logos next to each other. 28 | 2. About your team 29 | - This is a chance to share more about your project and what it does. 30 | - You can also highlight additional use cases for this new integration. 31 | 3. Why you chose to build on this tech stack 32 | - Illustrate the rationale for the relationship - why did you decide to work with Mintbase? 33 | - Describe the benefits of building on Mintbase (shared security, ease of use, ease of deployment, ease of interchain communication, decentralized, 34 | trusted, etc.) and why it was it important to have these features for your project. 35 | 4. Quote 36 | - Your CEO / CTO / Founder may want to include a quote of why they picked Mintbase to help gain more visibility and traction in the market. 37 | 5. Description of Mintbase 38 | - If you wish to mention Mintbase or Mintbase within the body of your text we recommend the following or similar: 39 | - "Mintbase funds research and development teams building the 40 | technology stack of the decentralized web. Nate Geier. Mintbase is the Foundation's flagship project." 41 | - "Mintbase is a scalable sharded chain and the first protocol that provides a secure environment for cross-chain composability across multiple shards. Mintbase also introduces a highly advanced, open governance system that will allow the network to innovate and grow at a much faster pace than legacy networks. Applications from DeFi to energy to gaming will thrive on Mintbase, challenging the centralized platforms of Web 2.0." 42 | 6. Social connections 43 | - The following text regarding Mintbase's social presence can be added at the end of your article: "Learn more about Mintbase by visiting their [website](https://mintbase.io/), and stay up to date with the latest developments by following them on [Medium](https://blog.mintbase.io/) or [Twitter](https://twitter.com/mintbase)." 44 | 45 | ## Recommended language 46 | 47 | 1. Use specific verbs such as integrate, support or build. 48 | 2. Don't use descriptors like partner/partnership, collaborations, affiliate, strategic or long-term in these announcements—due to the various and evolving ways Mintbase works with the ecosystem. 49 | 3. Don't describe your technology as the "first" to build on Mintbase—timing for launch implementations across all our projects is indefinite. 50 | 4. Don't indicate that Mintbase or Mintbase prefers a certain technology over all others: 51 | - As such, do not use: "Mintbase recommends that teams use this tech to build X" 52 | - Instead speak of the merits of the tech: "This technology provides great utility for the Mintbase network through..." 53 | 54 | We look forward to working with you in creating the next generation of the internet! If you have any questions or would like to be included in our next announcement, please email [grants@mintbase.io](mailto:grants@mintbase.io) 55 | -------------------------------------------------------------------------------- /docs/faq.md: -------------------------------------------------------------------------------- 1 | #### Mintbase Grants Program 2 | 3 | # Frequently Asked Questions 4 | 5 | - [🧭 General](#-general) 6 | - [🖊️ Application Process](#️-application-process) 7 | - [🥳 After Approval](#-after-approval) 8 | - [🚚 Milestone Delivery](#-milestone-delivery) 9 | 10 | ## 🧭 General 11 | 12 |
13 | How much can I ask for? 14 | 15 | Please refer to the [section on grant levels in our README](../README.md#level_slider-levels) for funding limits. 16 |
17 | 18 |
19 | What activities/positions do you fund? 20 | 21 | The Mintbase's Grants Program aims to fund software development and research activities that are beneficial for the ecosystem as a whole. As such, we don't usually fund tangential costs such as business-oriented activities (marketing, business planning), events or outreach, and—for non-infrastructure projects—deployment and hosting costs, maintenance or audits. We also expect you to have a good understanding of the technologies you are planning to use, meaning that we don't fund time spent learning how to use Mintbase or how to write ink! smart contracts. 22 |
23 | 24 |
25 | Can anyone apply? 26 | 27 | Projects for which a token sale has been or is being conducted are not eligible for a Mintbase grant. Other than that, there are no restrictions. 28 |
29 | 30 |
31 | Can I get an upfront payment? 32 | 33 | No. 34 |
35 | 36 |
37 | When do I get paid? 38 | 39 | Payments are issued once a milestone has been successfully delivered. By ‘successful’, we mean that our Grants team has reviewed _and officially accepted_ your submission. 40 |
41 | 42 |
43 | Can I reuse someone else’s open-source code? 44 | 45 | Open source software and the Mintbase movement are all about collaboration. As long as you meet the code’s license, we encourage you to find, modify and contribute to already existing libraries and projects if it is of use for your project. However, we expect you to honour other people’s work and their right to attribution, and your published code to adhere to the license requirements of the code you are benefiting from. Submitting code as part of a milestone that violates someone else’s license will result in immediate termination. We will furthermore continue to monitor any repositories you may have submitted as part of a milestone for possible license infringements and reserve the right to terminate the grant if we find you going out of your way to hide external contributions. 46 |
47 | 48 |
49 | I am starting a company that [...]. I want to use Mintbase to build a blockchain/parachain and connect [...]. Would I be eligible for a grant? 50 | 51 | We do not award grants to individual companies developing their private infrastructure. However, if part of your work is to build a library or another piece of software that could be of interest to the general Mintbase ecosystem and ask for funding specific to that, we are happy to look into it. 52 |
53 | 54 |
55 | My application was rejected. Do you have any recommendations on where to go from here? 56 | 57 | We usually give reasons why an application was rejected. We always try to be constructive and work with you towards an application that is beneficial to all parties. If we find no common ground, please have a look at [this section in our Grants Program readme](https://github.com/Mintbase/Grants-Program#rocket-alternative-funding-sources) for a list of alternative funding opportunities. 58 |
59 | 60 |
61 | One of your grantees is using my code without respecting the terms of its license. 62 | 63 | Please [reach out to us](mailto:grants@mintbase.io) asap. 64 |
65 | 66 |
67 | Why are other grant applications being accepted faster than mine? 68 | 69 | There are many reasons why your application might take longer than others: some applications are straightforward and simple and address an obvious issue, others require deeper understanding and discussion. If your application is highly technical or specialised, we might have to bring in an external evaluator. Sometimes, this specialised evaluator is busy with another evaluation. And sometimes, the committee is simply unsure or not quite convinced. 70 |
71 | 72 | 73 | ## 🖊️ Application Process 74 | 75 |
76 | How long does it take from application to decision? 77 | 78 | Depending on the requested amount, quality of the application and desirability for the ecosystem, a grant application could be approved within a week. Usually, there will be a discussion and requests for changes, additions or improvements. If no one in the committee finds the application approval-worthy or you don't react to our comments, it will be closed after two weeks of inactivity. Very large grants require the approval of the council, which convenes once a month. Thus, once an editor declares your application sufficient, it may take up to one month until a decision is made. 79 |
80 | 81 |
82 | A Mintbase member approved my application. Does that mean it is accepted? 83 | 84 | Depending on the size of the grant, applications require two to five committee members to approve it. Since we have many different members with different backgrounds and specializations, it is possible that the committee disagrees and your application gets rejected even though one or two members approved it. 85 | The application is accepted once the pull request is merged. 86 |
87 | 88 |
89 | How do I apply if I want to keep information private or want to be paid in fiat? 90 | 91 | For special cases that do not fit the regular grants structure, we provide [a form](https://docs.google.com/forms/d/e/1FAIpQLSfMfjiRmDQDRk-4OhNASM6BAKii7rz_B1jWtbCPkUh6N7M2ww/viewform). You can provide all application data by submitting this form, or submit the form with a reference to a pull request with data you are willing to make public. 92 |
93 | 94 | ## 🥳 After Approval 95 | 96 |
97 | When can I apply for a follow-up grant? 98 | 99 | Anyone who has successfully completed a grant project (i.e. all milestones were accepted, or the previous grant was terminated in mutual agreement) can apply for a follow-up grant. Concurrent grants are only granted in special circumstances. 100 |
101 | 102 |
103 | Something came up and I cannot finish the project in time. Can we postpone or call off the rest of my project? 104 | 105 | The Mintbase reserves the right to terminate an agreement that is behind schedule. However, we are not interested in taking away your grant for any slight hiccup. More often than not, delays are part of the journey and do not constitute a reason for concern. The best way to handle changes in your plans is to get in touch with us. If you would like to prematurely end your work, we can amend your application and remove the milestones you won't be able to complete. If you decide to continue work at a later date, you can always reapply for the remaining milestones and potentially adapt them to take into account any insights you have gained in the meantime. 106 |
107 | 108 |
109 | Can I list the Mintbase as a partner? 110 | 111 | No. Once the grants team has accepted your first milestone, you may display our [grants badge](https://github.com/Mintbase/Grants-Program/blob/master/docs/grant-badge-guidelines.md) in a project-specific context, such as the repository containing the grant project work. 112 |
113 | 114 |
115 | Can you help me advertise my project? 116 | 117 | The Mintbase does not provide PR services to its grantees. However, once per month we co-promote announcements from grants that have delivered a milestone on [Twitter](https://twitter.com/Mintbasefoundation). Note that the milestone needs to have been accepted prior to the announcement. Lastly, please observe our [announcement guidelines](https://github.com/Mintbase/Grants-Program/blob/master/docs/announcement-guidelines.md) for all grant-related communications. This document also lists an email address through which you can get in touch with our PR team for feedback and in case you have specific questions. 118 |
119 | 120 |
121 | I found one of my deliverables to be unnecessary, impossible or already done elsewhere. What do I do? 122 | 123 | Plans change. If you find parts of your original grant application to be unnecessary or you decide to pivot, but you still want to finish the project: get in touch with us. If your new plans are in line with the Mintbase’s values and the council approves the amendment, you can continue your work. If your plans change significantly or you find yourself not being able to finish the grant, we can mutually agree to terminate the grant early. You are always welcome to reapply another time. 124 |
125 | 126 | 127 | 128 | ## 🚚 Milestone Delivery 129 | 130 |
131 | How do I submit a milestone? 132 | 133 | For details, please refer to the [milestone delivery guidelines](./milestone-deliverables-guidelines.md) for the respective grants program. Generally speaking, the most important part of a delivery is a list of **the same deliverables listed in the application** with links to their implementation/realisation (ideally pointing to a specific commit or tag, so you can continue working on your repository without messing up your delivery and complicating our evaluation) and any additional notes you might have. The list of deliverables for each of your milestones should be defined in your grant agreement. 134 |
135 | 136 |
137 | Can I submit two or more milestones at once? 138 | 139 | You can. However, we strongly encourage you to submit your work in increments (milestones), so that you can be sure we didn’t misunderstand (an aspect of) your application, and you didn't make changes to your plan or delivery that would have required a reevaluation of the application. 140 |
141 | 142 |
143 | Can I add a badge to my repo once I’ve completed a milestone? 144 | 145 | If yours is a [Level 2 or 3](https://github.com/Mintbase/Grants-Program/blob/master/README.md#level_slider-levels) grant and your first milestone has been submitted **and accepted**, yes. Please make sure that you follow the [badge guidelines](https://github.com/Mintbase/Grants-Program/blob/master/docs/grant-badge-guidelines.md) when doing so. 146 |
147 | 148 |
149 | Why are other milestones being accepted or discussed faster than mine? 150 | 151 | While we try to process deliveries chronologically, some milestones aren't processed quite as fast as others. One obvious reason is the complexity of the delivery and its evaluation. Other times, your submission might require internal discussion or delegation. In any case, if you have any question on the processing of your delivery, you can reach out to us via email or Github. 152 |
153 | -------------------------------------------------------------------------------- /docs/grant_guidelines_per_category.md: -------------------------------------------------------------------------------- 1 | # Grant guidelines for most popular grant categories 2 | 3 | While we ask teams to provide details of their envisioned solution, we are aware that precise implementation might slightly differ from the initial specification. Should there be large deviations from the original plan, please communicate this to the Grants Team ahead of time. 4 | 5 | The list below serves only as a guide and is not exhaustive. 6 | 7 | ## Runtime Modules/Chains 8 | 9 | ### Applies to 10 | 11 | - Building/extending a Mintbase pallet 12 | 13 | ### Requirements 14 | 15 | - List the publicly exposed methods 16 | - For each method, specify (to the best of present knowledge): 17 | - Method signature (incl. parameters with their types, return type) 18 | - Short description (code template) 19 | - Runtime Storage defined by your module 20 | - [Use case diagram](https://www.wikiwand.com/en/Use_case_diagram) with e.g. UML or SysML (or similar tool demonstrating how external users/system components interact with one another) 21 | 22 | 23 | ## Development Tools 24 | 25 | ### Applies to 26 | 27 | - CLI tools 28 | - IDE / IDE plugin 29 | 30 | ### Requirements 31 | 32 | - State what programming language you'll use 33 | - Describe the commands that you want to make available to the users: 34 | - Name 35 | - Parameters 36 | - Result (value returned / file created or modified / application started etc.) 37 | 38 | 39 | ## UI Development 40 | 41 | ### Applies to 42 | 43 | - Building a web application with front-end components 44 | - Developing a mobile app 45 | 46 | ### Requirements 47 | 48 | - Provide mockups and/or wireframes (e.g. Figma) 49 | - List frameworks & tools for development & testing (e.g. React Native, Angular) 50 | 51 | ## Backend Development 52 | 53 | ### Applies to 54 | 55 | - Building a service/mobile app/webapp that relies on a back-end component 56 | 57 | ### Requirements 58 | 59 | - State what language & framework you'll use (e.g. python with Django, Rust with Rocket) 60 | - Define your database requirements and which system you'll use 61 | - Choose how & where will your backend be hosted (cloud provider, IPFS, localhost?) 62 | - Consider scaling & how you plan to handle it 63 | - Consider CI/CD 64 | - If you are (planning on) hosting the backend yourself, consider adding a [security.txt](https://securitytxt.org/) file so people can get in touch with you regarding (potential) security issues 65 | - Provide a link to your Github repository if you already have the structure in place 66 | 67 | 68 | ## Cryptography 69 | 70 | ### Applies to 71 | 72 | - New crypto library 73 | - Extending existing library's functionalities 74 | 75 | ### Requirements 76 | 77 | - Specify what programming language you'll use 78 | - Provide any publications/papers you will base your work on 79 | - Research other crypto libraries providing similar functionalities. State whether/how you plan to use their work. If they don't suit your needs, provide a detailed explanation why and what's missing 80 | - List any existing crypto libraries that you will use as reference implementation (e.g. in a different language) 81 | -------------------------------------------------------------------------------- /docs/milestone-deliverables-guidelines.md: -------------------------------------------------------------------------------- 1 | # Milestone Delivery Guidelines 2 | 3 | These are the guidelines to be followed for milestones submitted for evaluation. 4 | 5 | ## Submission 6 | 7 | Submission process will be created once the grants program beings July 1st 2022. 8 | 9 | ## Invoice 10 | 11 | Although a milestone needs to be reviewed and accepted, you can already submit your invoice through [this form](https://docs.google.com/forms/d/e/1FAIpQLSfmNYaoCgrxyhzgoKQ0ynQvnNRoTmgApz9NrMp-hd8mhIiO0A/viewform). 12 | 13 | ## Content 14 | 15 | The submission should contain the following information: 16 | 17 | - **Name of the grant project** 18 | - **Link to the open-source code/delivery** 19 | - **[License](#license)** 20 | - **[Documentation](#documentation)** 21 | - **[Formatted code](#formatted-code), according to a set of guidelines** 22 | - **[Testing Guide](#testing-guide)** 23 | - **A list of the [milestone deliverables](#milestone-deliverables)** 24 | - **Any [additional information](#additional-information)** 25 | 26 | ## License 27 | 28 | In order to successfully receive grant funding for your application it is necessary for the project to have open source code. 29 | We prefer Apache 2.0, but MIT or Unlicense are also acceptable. If your delivery comprises multiple repositories, make sure to include the license for each of them. 30 | 31 | ## Documentation 32 | 33 | We value high-quality open source code, but even the most performant code is of little use if it lacks proper documentation. 34 | 35 | We require that you document (where applicable): 36 | 37 | - API calls 38 | - Architecture overview and individual component details 39 | - Algorithms and protocols that are core to your project 40 | - Any other fundamental building blocks to your technology 41 | 42 | Unless absolutely necessary, make the documentation public as well, ideally as part of the appropriate code repository. This will make it easier for the community to use or adapt your project. 43 | 44 | **Note**: Only focus on your **own** contributions. Do not write detailed explanations of already existing components, e.g. IPFS. 45 | 46 | ## Formatted code 47 | 48 | A codebase that is easy to read is also easy to use. We suggest adopting one style from Day 1 and adhering to it across the entire team. 49 | This helps to keep the commit history clean and facilitates any reviews of the introduced changes. 50 | 51 | For **Mintbase**, we strongly recommend formatting your code according to the [official guidelines](https://github.com/paritytech/substrate/blob/master/docs/STYLE_GUIDE.md). 52 | 53 | For **Rust**, we encourage formatting any additional support libraries or helpers by following the [Style Guidelines](https://doc.rust-lang.org/1.0.0/style/README.html). 54 | 55 | For **any other** deliveries, please commit to a particular style & let us know which official guidelines you adopt. 56 | 57 | ## Testing Guide 58 | 59 | We require that each milestone delivery includes a comprehensive test suite, consisting of: 60 | 61 | ### A step-by-step guide demonstrating how your code achieves the milestones 62 | 63 | Please provide documentation on how to install, compile, run and test the deliverable(s). Make sure to include all necessary prerequisites. Common issues while replicating test results involve, among others, undocumented dependencies, version numbers, local database setups, breaking changes in the main branch since delivery, OS- and browser-specific incompatibilities. 64 | 65 | Depending on the deliverable, this could include (but is not limited to) 66 | 67 | - how to embed your library in another application, 68 | - how to make example API calls to your service, 69 | - running your web app, and 70 | - steps to complete some desired action in your mobile app. 71 | 72 | ### Unit tests 73 | 74 | As with any quality software project, each logical code component should be testable. 75 | 76 | ### Integration tests 77 | 78 | We prefer dockerfiles to avoid problems with versions and dependencies. 79 | 80 | 81 | **Note**: If you are not delivering code as part of your project, such a test suite is not applicable. This mainly applies to projects centering on design, research or hardware. If that is the case, please provide detailed instructions on how else we can test/run/replicate your deliverable. 82 | 83 | ## Milestone Deliverables 84 | 85 | Please provide a list of milestone deliverables. This list should closely reflect the list of deliverables agreed on in the Pull Request for the public **Grants Program** application or in Annex 1 of the grant contract for the private applications. 86 | 87 | Each item in the list should include a link to the deliverable itself, e.g.: 88 | 89 | - Google Doc link - make sure anyone with the link has View access 90 | - GitHub repository - include the appropriate file/folder in the link 91 | 92 | **Please highlight anything that deviates from the contract** and include further information that you think is relevant to the deliverable, either alongside the appropriate deliverable or under [Additional Information](#additional-information). 93 | 94 | Please ensure the repo has the correct open-source license. 95 | 96 | | Number | Deliverable | Link | Notes | 97 | | ------------- | ------------- | ------------- | ------------- | 98 | | 0a. | License | https://github.com/.../LICENSE | ... | 99 | | 0b. | Documentation | ... | ... | 100 | | 0c. | Testing Guide | ... | ... | 101 | | 1. | ... | ... | ... | 102 | | 2. | ... | ... | ... | 103 | 104 | ## Additional Information 105 | 106 | Please add any additional comments that you consider relevant for the evaluation. 107 | -------------------------------------------------------------------------------- /maintenance/maintenance-template.md: -------------------------------------------------------------------------------- 1 | # Mintbase Maintenance Grant Proposal 2 | 3 | > This document will be part of the terms and conditions of your agreement and therefore needs to contain all the required information about the project. Don't remove any of the mandatory parts presented in bold letters or as headlines! Lines starting with a `>` (such as this one) can be removed. 4 | > 5 | > See the [Maintenance Grants Process](../README.md#hammer_and_wrench-maintenance-grants) on how to submit a proposal. 6 | 7 | - **Project Code Name:** Code name of the project (e.g. JsonRPC Tools Maintenance) 8 | - **Team Name:** Legal name of your team (e.g. JsonCorp) 9 | - **Payment Address:** A NEAR account to where funds can be transfered (e.g. myproject.near) 10 | 11 | > ⚠️ *The combination of your GitHub account submitting the application and the payment address above will be your unique identifier during the program. Please keep them safe.* 12 | 13 | ## Project Overview :page_facing_up: 14 | 15 | If this application is in response to an RFP, please indicate this on the first line of this section. 16 | 17 | If this is an application for a follow-up grant (the continuation of an earlier, successful Mintbase grant), please provide name and/or pull request of said grant on the first line of this section. 18 | 19 | ### Overview 20 | 21 | Please provide the following: 22 | 23 | - If the code name of the project is not descriptive, a tag line (one sentence summary). 24 | - A brief description of the project. 25 | - How will the project you want to take for maintenance help the ecosystem of Mintbase / NEAR and what problems does it solve? 26 | - An indication of why your team is interested in supporting this project. 27 | - Outline of why the specific projects should continue being supported. 28 | 29 | ### Maintenance list 30 | 31 | Please provide a list of the repo(s) that need maintenance and further development: 32 | 33 | - https://github.com// 34 | - https://github.com// 35 | - https://github.com// 36 | 37 | ## Team :busts_in_silhouette: 38 | 39 | ### Team members 40 | 41 | - Name of team leader 42 | - Names of team members 43 | 44 | ### Contact 45 | 46 | - **Contact Name:** Full name of the contact person in your team 47 | - **Contact Email:** Contact email (e.g. john@duo.com) 48 | - **Website:** https://duo.com 49 | 50 | ### Legal Structure 51 | 52 | - **Registered Address:** Address of your registered legal entity, if available. Please keep it in a single line. (e.g. High Street 1, London LK1 234, UK) 53 | - **Registered Legal Entity:** Name of your registered legal entity, if available. (e.g. Duo Ltd.) 54 | 55 | ### Team's experience 56 | 57 | Please describe the team's relevant experience. If your project involves development work, we would appreciate it if you singled out a few interesting projects or contributions made by team members in the past. For research-related grants, references to past publications and projects in a related domain are helpful. 58 | 59 | If anyone on your team has applied for a grant at the Mintbase previously, please list the name of the project and legal entity here. 60 | 61 | ### Team Code Repos 62 | 63 | - https://github.com/ 64 | - https://github.com// 65 | - https://github.com// 66 | 67 | Please also provide the GitHub accounts of all team members. If they contain no activity, references to projects hosted elsewhere or live are also fine. 68 | 69 | - https://github.com/ 70 | - https://github.com/ 71 | 72 | ### Team LinkedIn Profiles (if available) 73 | 74 | - https://www.linkedin.com/ 75 | - https://www.linkedin.com/ 76 | 77 | ## Development Status :open_book: 78 | 79 | If you've already started implementing your project or it is part of a larger repository, please provide a link and a description of the code here. In any case, please provide some documentation on the research and other work you have conducted before applying. This could be: 80 | 81 | - links to improvement proposals or [RFPs](https://github.com/Mintbase/Grants-Program/tree/master/rfp-proposal) (requests for proposal), 82 | - academic publications relevant to the problem, 83 | - links to your research diary, blog posts, articles, forum discussions or open GitHub issues, 84 | - references to conversations you might have had related to this project with anyone from the Mintbase, 85 | - previous interface iterations, such as mock-ups and wireframes. 86 | 87 | ## Maintenance Responsibilities :nut_and_bolt: 88 | 89 | This section should specify what kind of tasks and responsibilities the maintainer team will cover during future development. If you have already outlined a list of issues/bugs or pull requests that need further development - you can specify them here to provide more context on what tasks you will close. 90 | 91 | Also, make sure the current project owners are willing to review/accept your contributions (a note here: if you're fully taking over the project, it will make more sense for the current owners to transfer the repository to your organization. If you can't get in touch with them, you may, of course, work on a fork). 92 | 93 | Below we provide **example maintenance responsibilities**. 94 | 95 | Issues we want to fix: 96 | - There's a bug in the JsonRPC library that affects its speed. 97 | - Massive lack of documentation and part of it is outdated. 98 | - Code has no comments, and it's tough for new developers to understand the code and contribute. 99 | 100 | Our responsibilities: 101 | - We will maintain the project's documentation. 102 | - We will answer issues and discussions. 103 | - We will fix new bugs as we receive and help contributors who have pull requests get any needed information. 104 | 105 | > ⚠️ *Note that all code should be published under an open-source license during the maintenance period.* 106 | 107 | ### Overview 108 | 109 | - **Start Date:** Date, when you plan to start with the maintenance work. 110 | - **Sprint/Period Duration:** Duration of the sprint/period (e.g. 4 weeks) 111 | - **Total Duration:** Duration of the entire maintenance contract (e.g. 1 year) 112 | - **Full-Time Equivalent (FTE):** Average number of full-time employees working on the project throughout its duration (see [Wikipedia](https://en.wikipedia.org/wiki/Full-time_equivalent), e.g. 2 FTE) 113 | - **Max budget per sprint/period:** Requested max budget in USD per sprint/period (e.g. 7,000 USD). Cost for each period need to be provided in USD; if the grant is paid out in USN, and potentially NEAR and nUSDC, the amount will be calculated according to the exchange rate at the time of payment. 114 | - **Hourly rate:** Amount of budget per hour, since it’s unlikely that the maintenance of the project requires the exact same workload each sprint. 115 | 116 | > ⚠️ *Note that you will need to provide a comprehensive report of the work done at the end of each month, including the list of issues/bugs/pull requests worked on, time spent on each of these, & finally, the associated cost. The time allocation & price will likely vary from month to month, depending on the nature of the project you're contributing to. The report should be in the form of a Milestone Delivery, again like the typical procedure. Mintbase will make the payments only after the successful merge of each individual report.* 117 | 118 | ## Future Plans 119 | 120 | Please include here 121 | 122 | - how you intend to use, enhance, promote and support the projects in the short term, and 123 | - the team's long-term plans and intentions in relation to it. 124 | 125 | ## Additional Information :heavy_plus_sign: 126 | 127 | **How did you hear about the Maintenance Grants Program?** Mintbase Website / Medium / Twitter / Element / Announcement by another team / personal recommendation / etc. 128 | 129 | Here you can also add any additional information that you think is relevant to this application but isn't part of it already, such as: 130 | 131 | - Work you have already done. 132 | - Whether there are any other teams who have already contributed (financially) to the project. 133 | - Previous grants you may have applied for. 134 | -------------------------------------------------------------------------------- /rfps/README.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | - [:grey_question: What is an RFP?](#grey_question-what-is-an-rfp) 4 | - [:mailbox_with_mail: Suggest an RFP](#mailbox_with_mail-suggest-an-rfp) 5 | 6 | 7 | ## :grey_question: What is an RFP? 8 | 9 | An RFP (Request for Proposals) is a declaration of interest for others to submit a grant application regarding a specific project. They usually revolve around issues that the author (often someone from our team, but [anyone can suggest one](/README.md#mailbox_with_mail-suggest-a-project)) deems useful and missing or unsolved in our ecosystem. 10 | 11 | If you find an open RFP here that you think you can address, feel free to [submit a grant application](../README.md#1-application). There is a [section in our application template](../applications/application-template.md#project-overview-page_facing_up) where you can reference the RFP you are addressing. 12 | 13 | ## :mailbox_with_mail: Suggest an RFP 14 | 15 | If you think that we should support the development of certain tools or projects (related to **Mintbase or NEAR**) that aren't in the Mintbase / NEAR, please submit a suggestion using the process described in our [Grants program README](../README.md#mailbox_with_mail-suggest-a-project). We are particularly interested in supporting projects that could be leveraged by other builders in our ecosystem. 16 | -------------------------------------------------------------------------------- /src/Grants2-template-1600x900.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Mintbase/Grants-Program/df25f02ee74c6148124ca2d78ac44cd116f1a3a1/src/Grants2-template-1600x900.png -------------------------------------------------------------------------------- /src/badge_black.svg: -------------------------------------------------------------------------------- 1 | web3 foundation grants -------------------------------------------------------------------------------- /src/like.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Mintbase/Grants-Program/df25f02ee74c6148124ca2d78ac44cd116f1a3a1/src/like.png -------------------------------------------------------------------------------- /src/map.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Mintbase/Grants-Program/df25f02ee74c6148124ca2d78ac44cd116f1a3a1/src/map.png -------------------------------------------------------------------------------- /src/medium.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Mintbase/Grants-Program/df25f02ee74c6148124ca2d78ac44cd116f1a3a1/src/medium.png -------------------------------------------------------------------------------- /src/reddit.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Mintbase/Grants-Program/df25f02ee74c6148124ca2d78ac44cd116f1a3a1/src/reddit.png -------------------------------------------------------------------------------- /src/rfp-header.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Mintbase/Grants-Program/df25f02ee74c6148124ca2d78ac44cd116f1a3a1/src/rfp-header.png -------------------------------------------------------------------------------- /src/twitter.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Mintbase/Grants-Program/df25f02ee74c6148124ca2d78ac44cd116f1a3a1/src/twitter.png -------------------------------------------------------------------------------- /src/web.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Mintbase/Grants-Program/df25f02ee74c6148124ca2d78ac44cd116f1a3a1/src/web.png -------------------------------------------------------------------------------- /src/youtube-play.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/Mintbase/Grants-Program/df25f02ee74c6148124ca2d78ac44cd116f1a3a1/src/youtube-play.png -------------------------------------------------------------------------------- /submissions/AmpleMintbase_milestone1_2024_09_27.md: -------------------------------------------------------------------------------- 1 | # Ample x Mintbase Streaming Royalty Claiming, Gated Function and Legal Doc Generator Builds 2 | ## Milestone 1: Smart Contract Royalty Claim & Gated Streaming Access Modules 3 | 4 | ### Deliverables 5 | 6 | | Number | Deliverable | Link | 7 | | ------------- | ------------- | ------------- | 8 | | - | Main repo | https://github.com/AmpleProtocol/launchpad | 9 | | 0a. | License | https://github.com/AmpleProtocol/launchpad/tree/master/LICENSE | 10 | | 0b. | Documentation | - [main](https://github.com/AmpleProtocol/launchpad/blob/master/README.md)
- [core](https://github.com/AmpleProtocol/launchpad/blob/master/core/README.md)
- [ui](https://github.com/AmpleProtocol/launchpad/blob/master/ui/README.md)
- [client](https://github.com/AmpleProtocol/launchpad/blob/master/client/README.md)
- [server](https://github.com/AmpleProtocol/launchpad/blob/master/server/README.md)
- [contracts](https://github.com/AmpleProtocol/launchpad/blob/master/contracts/README.md) | 11 | | 0c. | Testing guide | https://github.com/AmpleProtocol/launchpad?tab=readme-ov-file#testing-guide | 12 | | 0d. | Docker | https://hub.docker.com/r/menurivera/ample-launchpad-server | 13 | | 0e. | Article + video | https://youtu.be/H4EEH8ep2VU | 14 | | 1. | Mintbase module: Streaming Royalty Percentage Claims | https://github.com/AmpleProtocol/launchpad/blob/master/ui/src/components/Royalty.tsx | 15 | | 2. | Mintbase module: Gated Streaming Access Module | - https://github.com/AmpleProtocol/launchpad/blob/master/ui/src/components/Launch.tsx
- https://github.com/AmpleProtocol/launchpad/blob/master/ui/src/components/Player.tsx
- https://github.com/AmpleProtocol/launchpad/blob/master/ui/src/hooks/useStreaming.ts | 16 | | 3. | ~~NEAR chain integration~~
NPM packages | (We agreed upon an npm packages based approach, here are the links to them)
- [core](https://www.npmjs.com/package/@ample-launchpad/core)
- [client](https://www.npmjs.com/package/@ample-launchpad/client)
- [ui](https://www.npmjs.com/package/@ample-launchpad/ui) | 17 | 18 | ### Formtatted code 19 | 20 | #### TypeScript 21 | 1. `camelCase` for variables, functions and properties 22 | 2. `PascalCase` for Classes 23 | 3. `PascalCalse` with an `I` for interfaces (like `ISomeInterface`) 24 | 4. `CONSTANT_CASE` for constants 25 | 5. `camelCase` for files 26 | 27 | #### Rust 28 | 1. `snake_case` for variables, functions and properties 29 | 2. `PascalCase` for structs and impls 30 | 3. `CONSTANT_CASE` for constants 31 | 4. `snake_case` for files 32 | -------------------------------------------------------------------------------- /submissions/delivery_guidelines.md: -------------------------------------------------------------------------------- 1 | # Milestone Delivery Guidelines 2 | 3 | These are the guidelines to be followed for milestones submitted for evaluation. 4 | 5 | ## Content 6 | 7 | The submission should contain the following information: 8 | 9 | - **Name of the grant project** 10 | - **Link to the open-source code/delivery** 11 | - **[License](#license)** 12 | - **[Documentation](#documentation)** 13 | - **[Formatted code](#formatted-code), according to a set of guidelines** 14 | - **[Testing Guide](#testing-guide)** 15 | - **A list of the [milestone deliverables](#milestone-deliverables)** 16 | - **Any [additional information](#additional-information)** 17 | 18 | ## License 19 | 20 | In order to successfully receive grant funding for your application it is necessary for the project to have open source code. 21 | We prefer Apache 2.0, but MIT or Unlicense are also acceptable. If your delivery comprises multiple repositories, make sure to include the license for each of them. 22 | 23 | ## Documentation 24 | 25 | We value high-quality open source code, but even the most performant code is of little use if it lacks proper documentation. 26 | 27 | We require that you document (where applicable): 28 | 29 | - API calls 30 | - Architecture overview and individual component details 31 | - Algorithms and protocols that are core to your project 32 | - Any other fundamental building blocks to your technology 33 | 34 | Unless absolutely necessary, make the documentation public as well, ideally as part of the appropriate code repository. This will make it easier for the community to use or adapt your project. 35 | 36 | **Note**: Only focus on your **own** contributions. Do not write detailed explanations of already existing components, e.g. IPFS. 37 | 38 | ## Formatted code 39 | 40 | A codebase that is easy to read is also easy to use. We suggest adopting one style from Day 1 and adhering to it across the entire team. 41 | This helps to keep the commit history clean and facilitates any reviews of the introduced changes. 42 | 43 | 44 | For **Rust**, we encourage formatting any additional support libraries or helpers by following the [Style Guidelines](https://doc.rust-lang.org/1.0.0/style/README.html). 45 | 46 | For **any other** deliveries, please commit to a particular style & let us know which official guidelines you adopt. 47 | 48 | ## Testing Guide 49 | 50 | We require that each milestone delivery includes a comprehensive test suite, consisting of: 51 | 52 | ### A step-by-step guide demonstrating how your code achieves the milestones 53 | 54 | Please provide documentation on how to install, compile, run and test the deliverable(s). Make sure to include all necessary prerequisites. Common issues while replicating test results involve, among others, undocumented dependencies, version numbers, local database setups, breaking changes in the main branch since delivery, OS- and browser-specific incompatibilities. 55 | 56 | Depending on the deliverable, this could include (but is not limited to) 57 | 58 | - how to embed your library in another application, 59 | - how to make example API calls to your service, 60 | - running your web app, and 61 | - steps to complete some desired action in your mobile app. 62 | 63 | ### Unit tests 64 | 65 | As with any quality software project, each logical code component should be testable. 66 | 67 | ### Integration tests 68 | 69 | We prefer dockerfiles to avoid problems with versions and dependencies. 70 | 71 | 72 | **Note**: If you are not delivering code as part of your project, such a test suite is not applicable. This mainly applies to projects centering on design, research or hardware. If that is the case, please provide detailed instructions on how else we can test/run/replicate your deliverable. 73 | 74 | ## Milestone Deliverables 75 | 76 | Please provide a list of milestone deliverables. This list should closely reflect the list of deliverables agreed on in the Pull Request for the public **Grants Program** application or in Annex 1 of the grant contract for the private applications. 77 | 78 | Each item in the list should include a link to the deliverable itself, e.g.: 79 | 80 | - Google Doc link - make sure anyone with the link has View access 81 | - GitHub repository - include the appropriate file/folder in the link 82 | 83 | **Please highlight anything that deviates from the contract** and include further information that you think is relevant to the deliverable, either alongside the appropriate deliverable or under [Additional Information](#additional-information). 84 | 85 | Please ensure the repo has the correct open-source license. 86 | 87 | | Number | Deliverable | Link | Notes | 88 | | ------------- | ------------- | ------------- | ------------- | 89 | | 0a. | License | https://github.com/.../LICENSE | ... | 90 | | 0b. | Documentation | ... | ... | 91 | | 0c. | Testing Guide | ... | ... | 92 | | 1. | ... | ... | ... | 93 | | 2. | ... | ... | ... | 94 | 95 | ## Additional Information 96 | 97 | Please add any additional comments that you consider relevant for the evaluation. --------------------------------------------------------------------------------