├── .vscode └── settings.json ├── README.md ├── astar.png ├── banner.jpeg ├── buildersflow.png ├── hellowold.sol └── template.md /.vscode/settings.json: -------------------------------------------------------------------------------- 1 | { 2 | "code-runner.runInTerminal": true 3 | } -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Builders Program for Astar and Shiden Network 2 | 3 |

4 | 5 |

6 | 7 | > **:loudspeaker:** This builders program is tracked **transparently** on GitHub. For private submissions, please read more in this README file. 8 | > 9 | Other source: https://docs.astar.network/ecosystem/builders-program 10 | 11 | --- 12 | 13 | Please visit: https://astar.network/builders-program/ 14 | -------------------------------------------------------------------------------- /astar.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AstarNetwork/builders-program/25a4b49625a91c967d1524603c1099a640eb2d8c/astar.png -------------------------------------------------------------------------------- /banner.jpeg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AstarNetwork/builders-program/25a4b49625a91c967d1524603c1099a640eb2d8c/banner.jpeg -------------------------------------------------------------------------------- /buildersflow.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/AstarNetwork/builders-program/25a4b49625a91c967d1524603c1099a640eb2d8c/buildersflow.png -------------------------------------------------------------------------------- /hellowold.sol: -------------------------------------------------------------------------------- 1 | pragma solidity ^0.4.22; 2 | 3 | /* 4 | dApp staking whitelisted contract 5 | 6 | Project overview: 7 | 8 | 9 | We are part of the builders program, check out our proposal here: 10 | 11 | 12 | You can find us here: 13 | Telegram: 14 | Discord: 15 | Twitter: 16 | 17 | 18 | */ 19 | 20 | contract helloWorld { 21 | function renderHelloWorld () public pure returns (string) { 22 | return 'helloWorld'; 23 | } 24 | } 25 | -------------------------------------------------------------------------------- /template.md: -------------------------------------------------------------------------------- 1 | # Builders Program Application Template 2 | 3 | ## Project Overview 4 | 5 | **Project:** The name of the project 6 | 7 | Please provide a brief description of the project. 8 | 9 | ## Team 10 | 11 | ### Team members 12 | 13 | * Name of team leader 14 | * Names of team members 15 | 16 | ### Team Website 17 | 18 | * https:// 19 | 20 | ### Team's experience 21 | 22 | Please describe the team's work experience and history. If possible, please also share a few interesting projects that your team members contributed to and their role in those projects. 23 | 24 | ### Team Code Repos 25 | 26 | * https://github.com/ 27 | * https://github.com// 28 | * https://github.com// 29 | 30 | Please also provide the GitHub accounts of technical team members. 31 | 32 | * https://github.com/ 33 | * https://github.com/ 34 | 35 | ## Project Details 36 | 37 | In this section, please submit the following (where applicable): 38 | 39 | * An overview of the technology stack to be used 40 | * Wireframes of the UI 41 | * API specifications of the product 42 | * Documentation of core components, architecture etc. to be deployed 43 | * Details of a PoC / MVP that has been done previously 44 | 45 | ## Ecosystem 46 | 47 | Are there any other projects similar to yours? If so, how is your project different? Does your team already have some partnerships established? Can you share more details about these colllaborations? 48 | 49 | ## Development Roadmap 50 | 51 | Please break your development roadmap into a number of milestones and include instructions / information on how we can verify that these are the expected deliverables. When a milestone is being delivered, we will refer back to this contract to test that these functionalities exist in your product. An **example roadmap** is provided below. 52 | 53 | For each milestone: 54 | 55 | * include a specification of your software. There must be enough details to verify that the software meets the specification. 56 | * 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. 57 | * provide a test suite, comprising unit and integration tests, along with a guide on how to set up and run them. 58 | * commit to providing Dockerfiles for the delivery of your project. 59 | * **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). 60 | 61 | > If any of your deliverables are based on somebody else's work, please ensure that it is publish _under the terms of the license_ of the respective projects. You need to **highlight this in your milestone documentation and in the source code** where applicable! **Teams that submit others' work without attributing it will be immediately terminated.** 62 | 63 | ### Overview 64 | 65 | * **Total Estimated Duration:** Duration of the whole project (e.g. 2 months) 66 | * **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) 67 | 68 | ### Milestone 1 Example — Implement Substrate Modules 69 | 70 | * **Estimated duration:** 1 month 71 | * **FTE:** 2 72 | 73 | | Number | Deliverable | Specification | 74 | | -----: | ----------- | ------------- | 75 | | 0a. | License | Apache 2.0 / GPLv3 / MIT / Unlicense | 76 | | 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 Substrate nodes and send test transactions, which will show how the new functionality works. | 77 | | 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. | 78 | | 0d. | Docker | We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone. | 79 | | 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.) | 80 | | 1. | Substrate module: X | We will create a Substrate module that will... (Please list the functionality that will be implemented for the first milestone) | 81 | | 2. | Substrate module: Y | We will create a Substrate module that will... | 82 | | 3. | Substrate module: Z | We will create a Substrate module that will... | 83 | | 4. | Substrate chain | Modules X, Y & Z of our custom chain will interact in such a way... (Please describe the deliverable here as detailed as possible) | 84 | 85 | ### Milestone 2 Example — Additional features 86 | 87 | ... 88 | 89 | ### Community engagement 90 | 91 | Upon successful delivery of all milestones, it would be great if you produce an article/tutorial and publish it (for example on [Medium](https://medium.com/)). It should explain your work done as part of the grant. For larger projects it might make sense to publish multiple articles after the completion of different milestones. 92 | 93 | ## Future Plans 94 | 95 | Please include the team's long-term plans and intentions. 96 | 97 | ## Additional Information 98 | 99 | **How did you hear about the Builders Program?** Astar Network's Website / Medium / Twitter / Element / Announcement by another team / personal recommendation / etc. 100 | 101 | 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: 102 | 103 | * Work you have already done. 104 | * Whether there are any other teams who have already contributed (financially) to the project. 105 | * Previous grants you may have applied for. 106 | 107 | ## Credits (please remove this section from your application) 108 | 109 | Our Builders Program Application Template is a fork of [W3F's application template](https://github.com/w3f/Open-Grants-Program/blob/master/applications/application-template.md) with minor modifications. 110 | --------------------------------------------------------------------------------