Skip to content

Latest commit

 

History

History
132 lines (90 loc) · 7.93 KB

application-template.md

File metadata and controls

132 lines (90 loc) · 7.93 KB

Name of your Project

Project Overview

Please provide the following:

  • If the name of your project is not descriptive, a tagline (one sentence summary)
  • A brief description of your project
  • An indication of how your project relates to / integrates into Polkadot (SDK) / Kusama
  • An indication of why your team is interested in creating this project

Project Details

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):

  • An overview of the technology stack to be used
  • Documentation of core components, protocols, architecture, etc. to be deployed
  • PoC/MVP or other relevant prior work or research on the topic
  • Mockups/designs of any UI components
  • Data models / API specifications of the core functionality
  • What your project is not or will not provide or implement
    • This is a place for you to manage expectations and clarify any limitations that might not be obvious

Ecosystem Fit

Help us locate your project in the Polkadot/Kusama landscape and what problems it tries to solve by answering each of these questions:

  • Where and how does your project fit into the ecosystem?
  • Who is your target audience (parachain/dapp/wallet/UI developers, designers, your own user base, some dapp's userbase, yourself)?
  • What need(s) does your project meet?
  • How did you identify these needs? Please provide evidence in the form of (scientific) articles, forum discussions, case studies, or raw data.
  • Are there any other projects similar to yours in the Polkadot/Kusama ecosystem? Make sure to at least check the Polkadot Forum, the wiki's Tech Stack doc and OpenGov.
    • If so, how is your project different? Please identify and assess any projects addressing the same need and explain how your project is distinct. Feel free to include applicable research data, statistics, or metrics.
    • If not, please indicate why such a project might not have been possible, successful, or attempted.
  • Are there any projects similar to yours in related ecosystems?

Team

Please note that the data provided in this section is for administrative and informational purposes only. All beneficiaries of a grant must also be listed in the KYC/KYB process during the application phase.

  • Team Name: Name of your team. If you apply as a legal entity, please use its name.
  • Contact Name: Full name of the contact person in your team
  • Contact Email: Contact email
  • Website: Your website, GitHub org, blog, or similar

Team members

Please list the legal name of all grant beneficiaries.

LinkedIn Profiles (if available)

Team Code Repos

Please also provide the GitHub accounts of all team members. If they contain no activity, references to projects hosted elsewhere are also fine.

Team's experience

Please describe the team's relevant experience, such as Polkadot-related projects in progress or contributions to the ecosystem made by team members in the past.

Development Status

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:

  • academic publications relevant to the problem,
  • links to your research diary, blog posts, articles, forum discussions or open GitHub issues,
  • references to conversations you might have had related to this project with relevant actors in the ecosystem,
  • previous interface iterations, such as mock-ups and wireframes.

Development Roadmap

This section should break the development roadmap down into milestones and deliverables. 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. Below, we provide an example milestone with mandatory (0a to 0e) and example deliverables.

Please notice that Polkadot Open Source Grants only accept projects up to 3 months of duration and up to 2 milestones.

Overview

  • Estimated Duration: Duration of the whole project (e.g. 3 months)
  • Full-Time Equivalent (FTE): Average number of full-time employees working on the grant throughout its duration (see Wikipedia, e.g. 2 FTE)
  • Total Costs: Requested amount in USD for the whole project (e.g. 12,000 USD).

Note that deliverables 0a to 0e are mandatory. Please adapt their specification to your project.

Number Deliverable Specification
0a. License Apache 2.0 / GPLv3 / MIT / Unlicense. See the delivery guidelines for details.
0b. Documentation We will provide both inline documentation of the code and a basic tutorial that explains how a user can... See the delivery guidelines for details.
0c. Testing and Testing Guide Core functions will be fully covered by comprehensive unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. See the delivery guidelines for details.
0d. Docker We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone.
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.)
1. Pallet X We will create a Substrate module that will... (Please list the functionality that will be implemented for the first milestone. You can refer to details provided in previous sections.)
2. Smart contract Y The Y Substrate module will...
3. Substrate chain X and Y of our custom chain will interact in such a way... (Please describe the deliverable here as detailed as possible)
4. Library: ABC We will deliver a JS library that will implement the functionality described under "ABC Library"

Budget Breakdown (Example, please adapt)

Category: Budget Breakdown positions are split within the following categories:

  • Personnel
  • Equipment
  • Subcontracts/Subscriptions
Category Item Cost Amount Total Description
Personell Full-Stack Developer 8,000 USD 0.5 FTE 4,000 USD leading project with tech architecture and design
Personell Smart Contract Developer 10,000 USD 1 FTE 10,000 USD focused on execution and implementation
--- --- --- Total 14,000 USD

Future Plans

Please include here

  • how you intend to finance the project's long-term maintenance and development,
  • how you intend to use, enhance, and promote your project in the short term, and
  • the team's long-term plans and intentions in relation to it.

Additional Information

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:

  • Work you have already done
  • If there are any other teams who have already contributed (financially) to the project
  • Other funding you may have applied for