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

# ZHT\_Ticket Distribution

<figure><img src="/files/YTyRKE28sCNPCnMABPja" alt=""><figcaption></figcaption></figure>

**The total amount of ZHT\_tickets is 6 million, and these tickets can be exchanged for ZHT tokens at a 1:1 ratio. Therefore, each ticket has the same value as one ZHT token. By holding these tickets, you can exchange them to ZHT tokens.**&#x20;

**These tickets as designated for participants of the ZHunter launchpad participating in K STADIUM. The only place to get a ticket for the train that ZHunter is boarding is at the K STADIUM launchpad.**

***

\+ ZHT\_Ticket tokens can be send between users, but if they are lost or misplaced during transmission, they cannot be exchanged to ZHT tokens.

++ ZHT\_Tickets have the function of being exchanged for ZHT tokens, they cannot be transferred outside the K STADIUM wallet.

+++ ZHT\_Tickets will remain as ticket token during the lock-up period as designed in the token economy and will be exchanged for tokens afterwards.

++++ ZHT\_Tickets are automatically exchanged for ZHT tokens after the lock-up period.


---

# 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:

```
GET https://zhunter.gitbook.io/zhunter/zht_ticket/zht_ticket-distribution.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.