After having gone through a number of grant applications, the @zomg has refined the application template for clarity. We’ve included new sections/questions to help applicants think through demand validation. We’re also asking for more specific answers to the exact form of each deliverable, milestones, and metrics.
In the long term, we hope this results in applications that lead to more successful outcomes. In the short term, we believe these specifics will also lead to higher quality discussions with everyone on the forums.
Apply for your grants at the usual https://grants.zfnd.org/. The template is pasted below as well.
==================================================
If you have any doubts about the questions below, please reach out to anyone on the ZOMG on the Zcash forums.
Description of Problem or Opportunity
In addition to describing the problem/opportunity, please give a sense of how serious or urgent of a need you believe this to be. What evidence do you have? What validation have you already done, or how do you think you could validate this?
Proposed Solution
Describe the solution at a high level. Please be specific about who the users and stakeholders are and how they would interact with your solution. E.g. retail ZEC holders, Zcash core devs, wallet devs, DeFi users, potential Zcash community participants.
Solution Format
What is the exact form of the deliverable you’re creating? E.g. code shipped within the zcashd and zebra code bases, a website, a feature within a wallet, a text/markdown file, user manuals, etc.
Technical approach
Dive into the how of your project. Describe your approaches, components, workflows, methodology, etc. Bullet points and diagrams are appreciated!
How big of a problem would it be to not solve this problem?
Execution risks
What obstacles do you expect? What is most likely to go wrong? Which unknown factors or dependencies could jeopardize success? Who would have to incorporate your work in order for it to be usable?
Unintended Consequences Downsides
What are the negative ramifications if your project is successful? Consider usability, stability, privacy, integrity, availability, decentralization, interoperability, maintainability, technical debt, requisite education, etc.
Evaluation plan
What metrics for success can you share with the community once you’re done? In addition to quantitative metrics, what qualitative metrics do you think you could report?
Schedule and Milestones
What is your timeline for the project? Include concrete milestones and the major tasks required to complete each milestone.
Budget and Payout Timeline
How much funding do you need, and how will it be allocated (e.g., compensation for your effort, specific equipment, specific external services)? Please tie your payout timelines to the milestones presented in the previous step. Convention has been for applicants to base their budget on hours of work and an hourly rate, but we are open to proposals based on the value of outcomes instead.
Applicant background
Summarize your and/or your team’s background and experience. Demonstrate that you have the skills and expertise necessary for the project that you’re proposing. Institutional bona fides are not required, but we want to hear about your track record.