> For the complete documentation index, see [llms.txt](https://whitepaper.crypto-hunters.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.crypto-hunters.io/game-introduction/revenue-streams/game-tickets.md).

# Game tickets

The use of $CRH tokens to buy a ticket for a game provides several advantages over traditional payment methods.

* First, it eliminates the need for players to exchange their fiat currency for the game’s currency, which can be time-consuming and costly.
* Second, it provides an additional layer of security by allowing players to pay with a secure digital asset that is not subject to fraud or theft.
* Finally, it allows players to pay with a currency that is not subject to inflation or devaluation due to market fluctuations.

The use of $CRH tokens to buy tickets for the game will create additional buy volume and attract more investors in the Crypto Hunters ecosystem.


---

# 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://whitepaper.crypto-hunters.io/game-introduction/revenue-streams/game-tickets.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.
