> For the complete documentation index, see [llms.txt](https://docs.chiliz.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chiliz.com/community/developers-events/chiliz-sports-hackathon-july-2024/the-prize-money.md).

# The Prize Money

* **1st Place**: $10,000 (paid in instalments upon completing 3 milestones)
* **2nd Place**: $6,000 (paid in instalments upon completing 3 milestones)
* **Community Award**: $4,000 (paid in instalments upon completing 3 milestones)

Prize money will be split into 3 instalments and each instalment will be paid upon completing relevant milestone.

First installment: Winning a prize in the hackathon (33%)\
Second installment: Have the product fully operating on Chiliz Chain (mainnet). (33%)\
Third instalment: Have 50+ on-chain transactions (from unique addresses) per month for three months. (33%)

Additionally, winners will have the opportunity to:

* Feature in an upcoming Chiliz brand campaign.
* Gain exposure across the Web3 industry, attracting new users and investors.
* Receive support from the Chiliz team to build the creative side of your project.
* Promotion across Chiliz social media, email, and other marketing platforms.


---

# 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.chiliz.com/community/developers-events/chiliz-sports-hackathon-july-2024/the-prize-money.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.