> For the complete documentation index, see [llms.txt](https://sharpai.gitbook.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sharpai.gitbook.io/documentation/game-mechanics/prizes.md).

# Prizes

The prizes for Sharpai Legacy will be distributed as follows:

1. **Winner**: The player who either mints all 15 NFTs or has the most unique NFTs minted (in case of a tie, as explained in the Dynamics section) will receive 50% of the total collected funds.
2. **Random Sharpai NFT Drop Holder**: A random player holding Sharpai NFT drops will be selected to receive 10% of the total collected funds.
3. **Random Player**: A random player who participated in the game will be selected to receive 10% of the total collected funds.
4. **Referral Winner**: The player who refers the most individuals to the game will receive 10% of the total collected funds.

The Sharpai Legacy team will retain 20% of the total collected funds as compensation for their efforts in developing and maintaining the game.

## Example

Assuming 100,000 NFTs are minted during the game at an average price of $2 each, the total collected funds would amount to $200,000. The prize distribution would be as follows:

1. **Winner**: 50% of $200,000 = $100,000
2. **Random Sharpai NFT Drop Holder**: 10% of $200,000 = $20,000
3. **Random Player**: 10% of $200,000 = $20,000
4. **Referral Winner**: 10% of $200,000 = $20,000
5. **Team**: 20% of $200,000 = $40,000

This prize distribution structure ensures that multiple players have the opportunity to receive rewards, fostering an engaging and competitive environment throughout the game.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://sharpai.gitbook.io/documentation/game-mechanics/prizes.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 `build a script that syncs our docs to a CMS` 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.