> For the complete documentation index, see [llms.txt](https://organic-1.gitbook.io/organic-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://organic-1.gitbook.io/organic-docs/contributors/payout-formula.md).

# Payout Formula

These formulas show how we plan to split rewards, but the exact numbers like task weights, scoring rules, the boost cap, and the K parameter aren’t fixed. They’ll be proposed, tested, and ultimately decided by community votes, then adjusted over time as we learn what’s fairest and most effective.

### Payout Formula with Examples:

Let epoch revenue be **R** in SOL or USDC.\
Each task i has weight **W\_i**.\
Each user u has score **S\_u,i** in task i.\
Stake boost for user u is **B\_u = min(1 + sqrt(staked\_ORG\_u) / K, 1.25)**

* Task pool: `Pool_i = R * W_i / sum(W)`
* User share inside task: `Payout_u,i = Pool_i * (S_u,i * B_u) / sum(S * B)`

**Example**

* R = 2,000 USDC
* Two tasks with weights 9 and 3 so pools are 1,500 and 500
* In task 1 you have score 80 and boost 1.10
* Sum of all scores times boosts in task 1 is 800
* Your payout is 1,500 \* (80 \* 1.10) / 800 = 165 USDC


---

# 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://organic-1.gitbook.io/organic-docs/contributors/payout-formula.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.