Notice: The Helium grant program is evolving to better support grantees and innovation on the People's Network.
Past proposals submitted through GitHub will be viewable, but all new proposals will now be submitted through a simplified form. Take a look at this Notion doc for more details about the current Helium grant program submission process.
Template for Submission
Please create an issue in the grant repo and use the submission template below. After creating your issue in the grant repo, please complete this simple form to streamline the contract process and KYC. This form is the final step in the submission process and a lack of this information will delay the contract.
Project:
Project Name
Elevator Pitch:
This is your opportunity to convince the community of the impact and importance of your ask. This should be a brief description of the project that captures both the value and deliverable in a few sentences (or a tweet) and why it's needed or matters.
Total fiat/hnt ask:
This is the amount you're requesting for the grant, not necessarily the total budget.
Team or Project website: (optional)
Team or projects social: (optional)
Code Repos of team or key applicants:
(In lieu of public repos, please list a short bio of the applicants.)
https://github.com/organization
https://github.com/team-member-0
https://github.com/team-member-1
https://github.com/team-member-2
Project Details:
We expect a clearly articulated final deliverable for the project.
If the project utilizes legacy or other codebases, please specify this and link to applicable repos. In addition list any specific IP licenses you are utilizing.
Where relevant, please include mockups/designs of any UI/hardware components, and API specifications of the core functionality.
It is often helpful to include an overview of the tech stack to be used, including any required dependencies. Documentation of core components, protocols, architecture or schematics to be deployed within or as the MVP is even better.
Roadmap:
This section should break out the development roadmap into a number of milestones.
Since the milestones will appear in the grant contract, it helps to describe the expected functionality and how it can be validated.
Whenever milestones are delivered, we refer to the contract to ensure that everything has been delivered. The level of detail must be enough to later verify that the project meets the specification.
MS/Roadmap EXAMPLE:
| Milestone + Date | Deliverable | Summary | Cost |
|---|---|---|---|
| MS1, Date | Figma UI/UX | A figma ui/ux full tech stack defined, we estimate 40 developer hours | 5,000 USD |
| MS2, Date | On-chain functionality | Core features implemented on-chain and deployed to HNT testnet, estimated at 20 developer hours | 2500 USD |
| MS3, Date | MVP | -Docker delivered to the DeWi foundation for mainnet testing. - repo is public - A Medium article and tutorial written on how to implement the new add-on which is published and linked in discord and forums, estimated at 25 core team hours | 2750 USD |