> For the complete documentation index, see [llms.txt](https://guide.geyser.fund/geyser-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.geyser.fund/geyser-docs/product-guides/impact-funds/evaluation-process.md).

# Evaluation process

{% hint style="info" %}
Each Geyser Grant has its own theme, chosen by the Geyser team along with the sponsors. For example: [film grants](https://geyser.fund/grants/1), [gaming grants](https://geyser.fund/grants/4), and [education grants](https://geyser.fund/grants/5).
{% endhint %}

### Board voting

Board voting was the first evaluation process we used in practice. Here's how it works: 

* In accordance with the topic of the grant, the Geyser team **selects the board** of subject-matter experts.
* The board, through the vote of its component members, **evaluates** all applications and decides the **allocation** of the funds collected within a pre-determined time frame. 
* Subsequent to the deadline, Geyser **distributes** the funds to the projects in accordance with the allocation determined by the board. The grant is received as donations in sats to the selected Geyser projects.

<figure><img src="/files/PJhZqbjjljTtZqdjuaBk" alt=""><figcaption><p>The board of the first Geyser Grant</p></figcaption></figure>

### Community voting

The community votes for the winners of the Grant, but there are several voting logics in place:

1. **Proportional Voting**&#x20;

   In proportional Voting, 1 Satoshi = 1 Vote. Therefore, the more Sats sent, the more votes a project gets. This is&#x20;
2. Incremental Voting

   In incremental voting, there is a limit to the number a votes contributors can send, in order to ensure that all voters can make a difference.&#x20;

   Users must login for their contributions to count as votes, they can send contributions to multiple projects and send it multiple times to a single projects, but the number of votes a user can cast per project depends on contributions sent:

   **From 1k to 9,999 sats = 1 vote**

   **From 10k to 99,999 sats = 2 votes**

   **Above 100k sats = 3 votes**

<figure><img src="/files/Cr3EPo4hBzTt6spKdD6r" alt=""><figcaption><p>Example of community voting</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://guide.geyser.fund/geyser-docs/product-guides/impact-funds/evaluation-process.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.