As part of the EOS Network Foundation's (ENF) charter to grow and support the EOS ecosystem, the ENF has developed a multi-level grant program to help power research, software development, and maintenance of the EOSIO code base. For more information about the ENF, please visit our website, Medium blog, or YouTube account.

Individuals, small teams, and companies are all permitted to apply for grants. The purpose of the grants is to enable developers, businesses and individuals to build on EOS. Grants vary in size based on the size and scope of the initiative. All forms of projects are open for submission, core chain modifications, tools, libraries, etc. However, strong technical projects that clearly add to the Public Good are preferred. The odds of getting your project approved increase if you follow our acceptance recommendations. In all cases, you must meet the following minimum requirements.

The EOS Network Foundation (ENF) funds development grants for "Public Good" as well as those to “for profit” entities - with the goal that all grants will enhance the EOS community. Grants proposals are accepted in three levels, each having different amounts and acceptance criteria. ENF Grants have guidelines, an application process, and a multi-stage approval process. They also have a milestone based pay-out system.

There are three types of grants that the ENF considers. Some are originated by the community itself, and some are proposed in the form of an RFP by the ENF.

Most grant applications will take the form of a "New Proposal" from a member of the EOS community. These projects range from core chain enhancements, SDKs, tools, and applications. These are initiated by members of the community and run through the standard Grant Process below.

Maintenance grants are also initiated by the community to bring back support for a library, SDK or tool that has fallen out of maintenance. These proposals are more limited in scope and milestone to ensure proper progress is made. Maintenance grants should not be used to add feature or functionality to existing code, but to bring it up to current levels of the chain, operating system, or programming language levels. New functionality to existing projects can be applied via a "New Proposal". Read more about Maintenance Grants.

From time to time, the ENF will propose a work request to the community in the form of an RFP. All community members, teams and companies are welcome to reply to the RFP. Responses from multiple teams are expected. The ENF will then select the best RFP response and award the work to the team that submitted it. Read more on RFPs and how to reply to them.

The Grant Process consists of four major components: the Application Process, the Approval Process, Milestone Reporting, and Payment(s). Payments will be made in EOS to the wallet specified in the Grant Application. The processes must be completed in order and there may be feedback loops in some of the processes as described below.

The application process is completed through Github. You will need to fork the repository, change one of the forms, and submit it via a Pull Request as outlined in the steps below:

1. Fork this repository
2. In your fork, create a copy of the Grant Application template (applications/application-template.md). If you're using the GitHub web interface, you will need to create a new file and copy the contents of the template inside the new one. Please make sure you do not modify the template file directly.
3. Name the new file after your project: myproject_name.md.
4. Fill out the template with the details of your project. The more information you provide, the faster the review. Please refer to our Grant guidelines for most popular grant categories and make sure your deliverables present a similar level of detail. If you're only applying for a smaller grant that only consists of, say, UI work, you don't need to provide as much detail.
5. When your application is complete, create a Pull Request. Please note, the Pull Request should only contain one new file—the Markdown file you created from the template.
6. You will see a comment template that contains a checklist. You can leave it as is and tick the checkboxes once the pull request has been created. Please read through these items and check all of them.
7. Sign off on the terms and conditions presented by the CLA assistant bot as a Contributor License Agreement. You might need to reload the pull request to see its comment. 🔴🔴TED NEEDS TO FIGURE OUT HOW TO MAKE THIS WORK🔴🔴
8. Your Grant Application is now complete. The ENF Committee or Evaluators will contact your for next steps.

The Grant Approval Process consists of a review by the Grant Committee to check if the application fits the needs of the EOS Network community. If the Committee approves the application, it is then sent on to the Grant Evaluators for techincal approval. Please remember, your application will have a higher chance of acceptance and move through the process more quickly if you follow our acceptance recommendations and meet all of our minimum requirements. The approval process is outlined in the steps below:

1. The Grant Committee may issue comments and request changes on the pull request.
2. Clarifications and amendments made in the comments must be included in the application.
   • You may address feedback by directly modifying your application and leaving a comment once you're done.
   • Generally, if you don't reply within 2 weeks, the application will be closed due to inactivity, but you're always free to reopen it as long as it hasn't been rejected.
3. When all requested changes are addressed and the terms and conditions have been signed, your application will be marked as ready for review and shared internally with the rest of the committee.
4. Once the Grant Committee has agreed the application meets the needs of the EOS Network Community, it will be shared with the Grant Evaluators for techical evaluation. If it is determined that the application does not meet the needs of the EOS Community, it will be rejected with a reason as to why it did not meet those needs.
5. Similarly to the Grant Committee process, the Grant Evaluators may issue comments and request more information on your pull request.
6. Clarifications and ammendments to the above comments and request for information must be included in the application.
7. Once the application has received the required number of Evaluator approvals, it will be accepted and merged.
8. Applications may be rejected by the Grant Evaluators as being overly ambitious, improper architecture/design or inadequate architecture/design documentation.
9. Unless specified otherwise, the day on which the application is accepted will be considered the starting date of the project, and will be used to estimate delivery dates.

Milestones are to be delivered on the Grant Milestone repository following the process described therein.

Payments are made in EOS at the time of milestone sign off up to and including the final deliverable milestone.

There are three teams that drive the process for ENF Direct Grants: Committee, Evaluators, and Operations

The Grant Committee are senior members of the EOS community that know the priorities of the ecosystem and can make required initial funding decisions based upon the guidelines of the grant program. This committee is more business focused than technically focused but they understand the technical nature of the desired future.

• Yves La Rose
• Aaron Cox
• Dafeng Guo
• Fu Pan
• Peter Watt
• Van Kai
• Wen Huaqiang (might not be his github but looks possible)
• Damian Byeon

The Grant Evaluators review applications approved by the Grant Committee for technical merit and achievability. They are more technical in nature and are more concerned with whether the proposal solves the problem optimally, is realizable in the specified time frame, and utilizes proper processes as required for the milestone achievement metrics.

• Areg Hayrapetian
• Matt Witherspoon
• Bucky Kittenger
• Bart Wyatt
• Denis Carriere

The Grant Operations team manages the overall workflow of the ENF Grant process including: application acceptance and routing, notification of acceptance or rejection, monitoring of milestones and payment disbursals.

• Ted Cahall
• Jeff Werner

Apache License 2.0 © EOS Network Foundation