> 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/intro-to-geyser-grants.md).

# Intro to Geyser Grants

<figure><img src="/files/hTRkMp4aSEDGQSlOqGqE" alt=""><figcaption></figcaption></figure>

### The origin

[Brad Mill](https://twitter.com/bradmillscan)s and the Geyser team came up with the Geyser Grants as a way to support the development of the Bitcoin ecosystem by providing grants directly to creators.

Grants are not a new thing in Bitcoin, with projects like [HRF](https://hrf.org/devfund) and [Opensats](https://opensats.org/) providing much needed funding towards developers. But few grants were supporting Bitcoin creators - educators, creatives, or community builders. This is why we started Geyser Grants.

### **The why**

* Geyser Grants **reward and recognize** the work done by Bitcoin creators and builders
* Geyser Grants foster the creation of a **vibrant community** around crowdfunding
* Geyser Grants **promote a Bitcoin-only** philosophy through content and culture, and by supporting developments in this space

### Principles

1. **Bitcoin only**\
   We believe that bitcoin is the signal in the midst of the noise. Our aim is to remain bitcoin-only.
2. **Problem-solving oriented**\
   With Geyser Grants we aim to funnel funds towards what we believe are the biggest obstacles to hyperbitcoinization. For example:  85% of the world don’t speak English, means that we need more creators to translate Bitcoin content into many languages.
3. **Transparency**\
   We operate as transparently as possible by providing insights into:
   * where funds come from
   * how evaluations are carried out to select grant winners
   * how funds are distributed between grant winners
4. **Neutrality**\
   We operate without letting possible personal connections compromise any aspect of the grants. To achieve this, we've implemented a robust system, explained in [the next section](#how-it-works).

### How it works

1. **Where the money comes from**
   * **Bitcoin philanthropists**\
     We partner with Bitcoin philanthropists to provide funding towards creators providing value on the ground.
   * **Sponsorships**\
     We partner with other Bitcoin companies that are willing to spend some of their marketing budget towards the Bitcoin creator ecosystem.
2. **Who can apply**\
   In order to apply, a creator needs to have a project on Geyser. Anyone can create one quickly and for free. [Click here](/geyser-docs/product-guides/launch-a-project.md) for more information on how to get started.
3. **How the evaluation process works**\
   We have two evaluation processes in place:

   1. **Board voting**\
      We select a board of subject-matter experts to do the evaluation and the allocation of funds.
   2. **Community  voting**\
      Each donation to a project is worth as many votes as the size of the donation (for example, 1 sat = 1 vote). Funds are allocated proportionally to all votes cast within a pre-determined time period.

   Read our dedicated page to [learn more](/geyser-docs/product-guides/impact-funds/evaluation-process.md) about how the two processes work in practice.
4. **How funds are distributed**

   All funds are distributed as donations, according to the agreed allocation, to their respective Geyser projects.


---

# 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/intro-to-geyser-grants.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.