> 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/fund13-docs/project-onboarding/milestone-reviewers-guides/milestone-reviewer-rewards.md).

# Milestone Reviewer rewards

* Reward Structure: Instead of tying rewards to a single Statement of Milestones (SoM), rewards will now be allocated per unit of work for each individual milestone within the SoM.
  * This adjustment 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: ₳50
    * Eg SoM has three milestones in it - 3 x ₳50 ADA = ₳150 per entire SoM
    * Eg Som has six milestone in it - 6 x ₳50 ADA = ₳300 ADA per entire SoM
  * Per unit reward for a Proof of Achievement: ₳100


---

# 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://docs.projectcatalyst.io/previous-funds/fund13-docs/project-onboarding/milestone-reviewers-guides/milestone-reviewer-rewards.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.