Application Template

You may fork this template and fill in the details


At this stage, it is paramount the proposer provides as many details as possible so the team can provide better guidance and support. However, this can also just be the start of a conversation, so don’t lose sleep over this!
After your inquiry is submitted, the team will get in touch within 3-5 business days to get the conversation started. From there, the team will answer any questions you might have and ask you for more info if needed.


The combination of your GitHub account submitting the application and the payment address below together with your governance proposal number will be your unique identifier during the program. Please keep them safe.
  • The project name:
  • Summary of your project and how it would help our ecosystem:
  • Team Name:
  • Payment address (fx address, 0x address - Specify network and currency):
  • The level of amount you are requesting for? Level 1,2, 3, 4:
  • Category your project belongs to:
If you're inquiring as an individual, you can just give your own name (this doesn't need to be a legal name at this point - we just want to know what name you'd like us to use when we get in touch).

Project Description

Tell the team as much about your project as you can, and do consider the following details (where relevant).


  • Stage of your project (just an idea, already in progress, proof of concept or prototype)
  • Main goals and planned approach
    • Does the project roadmap fit broadly into the FunctionX/PundiX Chain roadmap?
  • Online resources (website, research papers, articles, blog posts, GitHub, etc)
  • Mockups/designs of any UI components Data models / API specifications of the core functionality
  • An overview of the technology stack to be used
  • Documentation of core components, protocols, architecture, etc. to be deployed
  • What your project is not or will not provide or implement
    • This is a place for you to manage expectations and to clarify any limitations that might not be obvious

Team profile

If you're part of a team, include any member of your team who is working on the project you're inquiring about. This is open-ended and you can share anything you think is relevant. You may single out a few interesting projects or past publications.


  • Contact details
    • Name of team leader:
    • Names of team members:
    • Contact Name: Full name of the contact person in your team
    • Contact Email: Contact email (e.g. [email protected])
    • Website:
  • For companies/corporations
    • 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)
    • Registered Legal Entity: Name of your registered legal entity, if available. (e.g. Duo Ltd.)
    • Team’s experience
      • Team Code Repos
      • Team member’s individual repos
      • Team’s LinkedIn Profiles (if available) or other professional social media
Showcasing past projects and your team's track record will definitely help in your proposal's chances of being successful. Additionally, the more details about your project the better, especially with regards to the research you have made and the careful planning of your project.

Ecosystem Fit/Impact

As an organization, the team will focus on doing what's best for Function X. So, it is important you describe how your work will benefit the Function X ecosystem.


  • Where and how does your project fit into the ecosystem?
  • What problem are you solving?
  • Who is your target audience (parachain/dapp/wallet/UI developers, designers, your own user base, some dapp's userbase, yourself)?
  • Who will benefit, and how: what tools or opportunities will people have that they didn't have before? What will be possible that wasn't possible before? Do you have anything tangible to give back to the community like airdrops?
  • What need(s) does your project meet?
  • Are there any other projects similar to yours in other EVM/Cosmos ecosystem?
    • If so, how is your project different?
    • If not, are there similar projects in related ecosystems?
Having tangibles to give back to the community will certainly help with the success of your proposal.

Development status

If you've already started implementing your project or if 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.


  • 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 anyone from the Web3 Foundation
  • Previous interface iterations, such as mock-ups and wireframes
  • What are the most significant obstacles facing your project or your team right now?
    • Difficulty finding support or community
    • Technical dilemmas
  • What are some of your most pressing needs?
    • Feedback and direction
    • Collaborations or connections with other teams, mentors, advisors
⚠️ At the inquiry stage, you will only need to fill the template up to this part. Development status will help us understand your needs better and help us provide better assistance to you beyond financial support.

Associated costs

This segment is to show all the costs your project requires including any research of how you arrived at those costs, including any assumptions made.


  • Is the budget plan reasonable?
  • How do you plan on using the fund?
  • Clear breakdown of associated costs?
    • If you are spending funds on hiring developers, you can state their qualifications and how much you expect to pay them.
    • You can also mention the server costs and other miscellaneous costs associated with the project.
  • If you intend to redistribute part or total of the requested funds in any manner, please specify how you intend to do it, and how community funds will serve the general FunctionX purpose and not a specific purpose.
Detailed research on associated costs and any assumptions on how you arrived at that figure will definitely help your proposal.

Development Roadmap

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. 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 roadmap. In the descriptions, it should be clear how your project is related to Function X. We recommend that teams structure their roadmap as 1 milestone ≈ 1 month.
For each milestone:
  • 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.
  • Include the amount of funding requested per milestone.
  • 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.
  • Provide a test suite, comprising unit and integration tests, along with a guide on how to set up and run them.
  • Commit to providing Dockerfiles for the delivery of your project.
  • Indicate milestone duration as well as number of full-time employees working on each milestone.
  • 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).
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.


  • Total Estimated Duration: Duration of the whole project (e.g. 2 months)
  • Full-Time Equivalent (FTE): Average number of full-time employees working on the project 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 the acceptance criteria and additional benefits vary depending on the level of funding requested. This and the costs for each milestone need to be provided in USD; if the grant is paid out in FX, the amount will be calculated according to the exchange rate at the time of payment.
Milestone 1 Example — Implement Substrate Modules
  • Estimated duration: 1 month
  • FTE: 2
  • Costs: 8,000 USD
Apache 2.0 / GPLv3 / MIT / Unlicense
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.
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.
We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone.
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.)
First component of the project
Milestone 2 Example — Additional features
  • Estimated Duration: 1 month
  • FTE: 1
  • Costs: 4,000 USD

Future plans

Post delivery of your project, how would you want to maintain and manage your project?


  • How you intend to use, enhance, promote and support your project in the short term.
  • The team's long-term plans and intentions in relation to it.
  • Your strategy to maintain the project beyond the duration of the grant.