|
| 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 | +- **LAND OF CLANS** |
| 8 | +- **Indie team: Alex&Serg** |
| 9 | +- **thegame_dao.near** |
| 10 | +- **2** |
| 11 | + |
| 12 | +## Project Overview :page_facing_up: |
| 13 | + |
| 14 | +### Overview |
| 15 | + |
| 16 | +"Land of Clans" is a v2 of popular multiplayer, strategy game on NEAR - but this time with GameFi2.0 economical model. |
| 17 | +(v1 has a classic play-to-earn economical model.) |
| 18 | + |
| 19 | +Our first game version "Land to Empire" launched on NEAR on February 2022. |
| 20 | +Our Statistic for two years online on NEAR: |
| 21 | + 5.5K players |
| 22 | + 197K p2p battles |
| 23 | + 166K buildings |
| 24 | + 33K token transfers |
| 25 | + 27K nft transfers |
| 26 | + 21K awards |
| 27 | + |
| 28 | +Our NFT collection is in TOP Mintbase Games - https://www.mintbase.xyz/explore/Gaming/0 |
| 29 | + |
| 30 | +### Project Details |
| 31 | + |
| 32 | +"Land of clans" - is a strategy game with implemented GameFI2.0 economical model based on DeFi’s style NFT-Pools and AMM. |
| 33 | +We are pushing the idea of GameFi2.0 so that there will be more games with stable economies in the World. |
| 34 | + |
| 35 | +Game landing page - https://www.landofclans.io/ |
| 36 | + |
| 37 | +GameFi2.0 = GameFi + NFT-pool + AMM |
| 38 | + |
| 39 | +The idea is simple - we create an NFT-pool contract, and players' payments will fill this pool with liquidity. All along the lines of miners and stakers and those who add liquidity to DeFi. Someone without finances spends his time mining resources in the game (Proof-of-Game). Another one with liquidity buys up the first mined resources and adds liquidity to the pool. Others, who have just started playing and have funds, buy resources in the pool to catch up with those who have been playing for a long time. |
| 40 | +We create the rules, and players come up with strategies to earn money, often they surprise us and it's great. It is already good, the money is publicly controlled and does not leak out of the project to the unknown. |
| 41 | + |
| 42 | +And what we get at the start is an NFT-pool without NFTs, but with liquid tokens. |
| 43 | + |
| 44 | +Then we connect the AMM (Automatic Market Maker) contract, which contains a price list of all types of NFTs and regulates their rates. |
| 45 | + |
| 46 | +And then the players who minted NFTs and want to sell them - will be able to swap them for tokens at the rate of AMM. Example how work AMM: |
| 47 | +The price of the NFT is 200. |
| 48 | +You sell the NFT for 200. |
| 49 | +AMM will put it on the market for 210 and drop the purchase price to 195. |
| 50 | +The next player sells the NFT for 195. |
| 51 | +AMM will put it up for sale for 205 and lower the purchase price to 190. |
| 52 | +If there are no sales for a while, AMM will raise the price to 191, then 192, and so on. |
| 53 | +AMM's task is to adjust the price so that it reflects the value of each NFT. |
| 54 | + |
| 55 | +If there are a lot of sales - this is a sign that the value of the resource is lower than its value and AMM will lower the price of that type of NFT. If players on the contrary buy NFTs - their value is higher than the current price, AMM will raise the price of them. |
| 56 | +And thus very quickly the price will be adjusted and will reflect the real value of each type of NFT in the game. |
| 57 | + |
| 58 | +All purchased NFTs, AMM automatically puts on sale with a markup of 5-10%, which will go to the earnings of NFT-pool. |
| 59 | + |
| 60 | +### Ecosystem Fit |
| 61 | + |
| 62 | +The ecosystem will get open-source NFT pool contracts and AMM (Automatic Market Maker). |
| 63 | +This would be a great addition to the functionality of Mintbase. |
| 64 | + |
| 65 | +We are ready to be pioneers and show the NEAR ecosystem all the benefits of the revolutionary economic model, the increase in the number of user transactions it brings and how much more stable the economic models are. |
| 66 | + |
| 67 | +## Team :busts_in_silhouette: |
| 68 | + |
| 69 | +### Team members |
| 70 | + |
| 71 | +Founders are developers with 10+ years of commercial experience and startup building. |
| 72 | +- Alex CEO |
| 73 | +- Serg CTO |
| 74 | +We are located in the UK and Poland. |
| 75 | + |
| 76 | +### Contact |
| 77 | + |
| 78 | +- Alexander Kolesnikov |
| 79 | + |
| 80 | +- https://www.landofclans.io/ |
| 81 | + |
| 82 | +### Legal Structure |
| 83 | + |
| 84 | +We're in the process of re-registering to another jurisdiction, and in the interim, the current address is: |
| 85 | +- Office 145, floor 12,Building: Owned by RASHED MOHAMMED ABDULLA ALMAZROUEI, street Al Thanyah 1 Dubai, UAE. PObox: 450450 |
| 86 | +- ONLYSPACE ONLINE GAMING SERVICES EST. |
| 87 | +- License id: 1027669 |
| 88 | + |
| 89 | +### Team's experience |
| 90 | + |
| 91 | +Since 2015, we have become evangelists of blockchain technology. We participated in the development of AML and KYC platforms. We launched private blockchains for financial institutions. We have developed several open source libraries that have become quite popular. In addition, we launched three games, got great feedback and engagement from our users and continue to improve in this direction. |
| 92 | + |
| 93 | +### Team Code Repos |
| 94 | + |
| 95 | +https://github.com/land2empire |
| 96 | +https://github.com/near-rails-guide/near_api |
| 97 | +https://github.com/near-rails-guide/borsh-rb |
| 98 | +https://github.com/near-rails-guide/near-rails-demo |
| 99 | + |
| 100 | +https://github.com/2rba |
| 101 | +https://github.com/k-o-l-e-s |
| 102 | + |
| 103 | +### Team LinkedIn Profiles (if available) |
| 104 | + |
| 105 | +- https://www.linkedin.com/in/koles/ |
| 106 | +- https://www.linkedin.com/in/serge-tyatin/ |
| 107 | + |
| 108 | +## Development Status :open_book: |
| 109 | + |
| 110 | +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: |
| 111 | + |
| 112 | +- links to improvement proposals or [RFPs](https://github.com/mintbase/Grants-Program/tree/master/rfp-proposal) (requests for proposal), |
| 113 | +- academic publications relevant to the problem, |
| 114 | +- links to your research diary, blog posts, articles, forum discussions or open GitHub issues, |
| 115 | +- references to conversations you might have had related to this project with anyone from the Mintbase Foundation, |
| 116 | +- previous interface iterations, such as mock-ups and wireframes. |
| 117 | + |
| 118 | +## Development Roadmap :nut_and_bolt: |
| 119 | + |
| 120 | +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. |
| 121 | + |
| 122 | +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. |
| 123 | + |
| 124 | +For each milestone, |
| 125 | + |
| 126 | +- 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. |
| 127 | +- include the amount of funding requested _per milestone_. |
| 128 | +- 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. |
| 129 | +- provide a test suite, comprising unit and integration tests, along with a guide on how to set up and run them. |
| 130 | +- commit to providing Dockerfiles for the delivery of your project. |
| 131 | +- indicate milestone duration as well as number of full-time employees working on each milestone. |
| 132 | +- **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). |
| 133 | + |
| 134 | +> :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.** |
| 135 | +
|
| 136 | +### Overview |
| 137 | + |
| 138 | +- **Total Estimated Duration:** Duration of the whole project (e.g. 2 months) |
| 139 | +- **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) |
| 140 | +- **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. |
| 141 | + |
| 142 | +### Milestone 1 Example — Implement Mintbase Modules |
| 143 | + |
| 144 | +- **Estimated duration:** 1 month |
| 145 | +- **FTE:** 2 |
| 146 | +- **Costs:** 8,000 USD |
| 147 | + |
| 148 | +| Number | Deliverable | Specification | |
| 149 | +| -----: | ----------- | ------------- | |
| 150 | +| 0a. | License | Apache 2.0 / GPLv3 / MIT / Unlicense | |
| 151 | +| 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. | |
| 152 | +| 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. | |
| 153 | +| 0d. | Docker | We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone. | |
| 154 | +| 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.) |
| 155 | +| 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) | |
| 156 | +| 2. | Mintbase module: Y | We will create a Mintbase / NEAR module that will... | |
| 157 | +| 3. | Mintbase module: Z | We will create a Mintbase / NEAR module that will... | |
| 158 | +| 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) | |
| 159 | + |
| 160 | +### Milestone 2 Example — Additional features |
| 161 | + |
| 162 | +- **Estimated Duration:** 1 month |
| 163 | +- **FTE:** 1 |
| 164 | +- **Costs:** 4,000 USD |
| 165 | + |
| 166 | +... |
| 167 | +## Future Plans |
| 168 | + |
| 169 | +Please include here |
| 170 | + |
| 171 | +- how you intend to use, enhance, promote and support your project in the short term, and |
| 172 | +- the team's long-term plans and intentions in relation to it. |
| 173 | + |
| 174 | + |
| 175 | +## Additional Information :heavy_plus_sign: |
| 176 | + |
| 177 | +**How did you hear about the Grants Program?** Mintbase Website / Medium / Twitter / Element / Announcement by another team / personal recommendation / etc. |
| 178 | + |
| 179 | +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: |
| 180 | + |
| 181 | +- Work you have already done. |
| 182 | +- If there are any other teams who have already contributed (financially) to the project. |
| 183 | +- Previous grants you may have applied for. |
0 commit comments