Grants Program Framework

As the Pilot League, we want to grow the Idle ecosystem by rewarding the work of users and developers in the community. For this reason, we have created a framework to manage the grants that we will be distributed from now on.

Dev Grants Ecosystem Growth (integrations, user-related features, UI/UX) Yes (off-chain)
Protocol R&D (optimizations, new gov/fees modules, security) Yes (off-chain and on-chain)
Community Grants Educational (educational video and written content about Idle’s protocol and the multi-language translation of these No
Challenges (challenges/contests on different themes in which users can participate and win prizes) No
Idle Heroes Bounty (be the hero of Idle: talk about Idle on social networks, spread the word, actively participate in discussions in the Idle gov forum, and get rewarded) No

How to apply for grants

Check the forum and the community roadmap to know if there is already a discussion about the idea you want to propose; if so, you have to write and apply on the same post already created by another user or the Pilot League.

Regarding a new idea to propose for a grant:

  • Each new proposal must be posted in the right subcategory of the grants proposal category on the Idle gov forum.
  • if it is included in the community roadmap but it isn’t assigned yet, copy the specific Trello card’s link and write it in the proposal application.

To apply for grants and to propose your idea, follow these steps:

Start a new thread in the forum, and chose the GRANT CATEGORY that fits your proposal (either “:desktop_computer: Dev Grant” or “:cyclone: Community Grant”).

Title: [SUBCATEGORY] “your title here” – Please include a clear and concise title, beginning with the specific grant subcategory you refer to; as you see, bounties programs (e.g., Idle Heroes) are not included since they do not require any proposal to be created.

  1. Abstract: Briefly describe the idea and the benefits you intend to achieve with the proposed changes for Idle protocol or how your proposal can benefit the community. KISS, and understandable by non-technical community members.
  2. Scope of the Work: Describe the technical specifications to implement the idea. Specify tech & approach you will use to develop it. Keep it schematic and try to describe all required specs. Include sufficient details and explicit action points.
  3. Discussion Links: Link initial post or previous discussions, and any useful resource that might help understand the technical implementation (eg docs, white papers, …)
  4. Bio & Background: Briefly introducing yourself (or the team) and any past works. Applicants can remain anonymous, but past works should be mandatory to evaluate the skills of the developer if you are applying for Dev Grants.
  5. Budget: Provide a quote in $IDLE tokens to deliver the idea
  6. Timeline: Provide a roadmap/timeline for the assignment (if you are applying for Challenges Grant you can skip this point, since you will follow the timeline provided by the Pilot League)

How the Pilot League awards grants

The following points address how the Pilot League will choose Dev Grants proposals and how the prioritization of these into the roadmap works.

Instead, regarding Community Grants we believe these should be handled more directly and independently by the Pilot League.

  • The Pilot League will award grants after a careful analysis.
  • The ideas that the Pilot League will choose will be included in the backlog of the community roadmap.
  • Periodically, the Pilot League will ask the community of Idle, through a snapshot, to prioritize the backlog, namely which of the proposals in the backlog should be moved in the discussion phase, managing and assigning them before the others.
  • Since that moment, the Pilot League will discuss with the community the ideas included in the discussion phase column of the community roadmap. It will decide whether to go ahead with all the ideas or only some of them, depending on the community feedback and the mandate budget for that month.