> For the complete documentation index, see [llms.txt](https://docs.projectcatalyst.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.projectcatalyst.io/previous-funds/fund14-docs/project-onboarding/milestone-reviewers-guides/milestone-reviewer-rewards.md).

# Milestone Reviewer rewards

**Reward Structure**: Rewards are allocated per unit of work for each individual milestone within the SoM.

* This aims to distribute rewards more fairly based on the size of each SoM.
* Smaller SoMs will receive lower rewards, while larger SoMs will receive higher rewards.

**Specific Reward Amounts**:

* Per unit reward for a milestone review of an SoM: **₳75**
  * Eg SoM has three milestones in it - 3 x ₳75 ADA = ₳225 per entire SoM
  * Eg Som has six milestone in it - 6 x ₳75 ADA = ₳450 ADA per entire SoM
* Per unit reward for a Proof of Achievement: **₳150**


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.projectcatalyst.io/previous-funds/fund14-docs/project-onboarding/milestone-reviewers-guides/milestone-reviewer-rewards.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.