# ZHT\_Ticket Ecosystem

<figure><img src="https://3001192518-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM8v7FghmUgMZhVOJR1uk%2Fuploads%2FHvMX8wcaPp2Hx3OsmEdM%2F%EC%A0%9C%EB%AA%A9%EC%9D%84-%EC%9E%85%EB%A0%A5%ED%95%B4%EC%A3%BC%EC%84%B8%EC%9A%94_-001%20(1).jpg?alt=media&#x26;token=20cf7240-06f4-4e08-9521-0d178a985cec" alt=""><figcaption></figcaption></figure>

The ZHT ticket holds the same value as the ZHT token and will be dropped after the launchpad ends. These tickets have been prepared to give K STADIUM users, who use the ZHunter dApp on the mainnet, the opportunity to participate as initial contributors.

The purpose of the ZHT ticket is to facilitate the exchange for ZHT tokens. According to the ZHunter roadmap, after the launchpad, we will immediately begin working on simultaneous listing and launching on a centralized exchange (CEX).

The primary goal of ZHunter is to list on a CEX to attract more global users and expand our presence in the crypto market. Through strategic partnerships with various global partners, we aim to conduct events to raise awareness of ZHunter.


---

# Agent Instructions: 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-ecosystem.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.