> For the complete documentation index, see [llms.txt](https://docs.qzino.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qzino.com/getting-started/lottery.md).
# Lottery
The Qzino Lottery is a weekly draw that uses a 100% RTP model. It's designed to add an additional layer of engagement and rewards to the platform.
By combining platform revenue, QZI token utility, and recurring draws, the Qzino Lottery transforms passive participation into an ongoing opportunity to win. Whether tickets are formed through holding QZI or purchased directly, the lottery is seamlessly integrated into the Qzino ecosystem — rewarding active users and long-term supporters alike.
**How the Lottery Works**
Each lottery ticket consists of 6 numbers:
* 5 main numbers
* 1 Powerball number
To win, the numbers on your ticket must match the winning combination in the exact same order. The number of correctly matched numbers (and their order) determines the prize tier.
The more numbers you match correctly, the higher the reward. If multiple users win the same prize tier, the prize pool for that tier is split equally among all winners.
{% hint style="info" %}
**Draws will take place once per week.**
{% endhint %}
**Prize Pool Funding**
The lottery prize pool is funded through two independent sources:
* 5% of Qzino’s NGR generated in USDT
* 2% allocated from QZI tokenomics
This dual funding model ensures continuous prize pool growth.
**How to Obtain Lottery Tickets**
Users can obtain lottery tickets in two ways:
1. Purchase with QZI
Tickets can be formed based on your QZI balance. As long as your balance covers the required ticket value, those tickets remain active for future draws.
2. Purchased with other supo
Tickets can also be purchased directly using other supported currencies. These tickets are valid for a single draw.
**Ticket Lifecycle & Burning Rules**
* Tickets formed with QZI
Do not burn after the draw and can continue participating in future lotteries, provided they remain fully covered by your QZI balance.
* Tickets purchased with other currencies
Are single-use and burn automatically after the draw.
Before each draw, the system validates all tickets against your current QZI balance:
* If your balance decreases, the number of covered tickets is recalculated
* Any tickets no longer backed by sufficient balance are burned before the draw and do not participate
This ensures fairness and prevents over-allocation.
**Order of Numbers**
Order matters. To qualify for any prize tier, your ticket numbers must match the winning numbers in the exact same sequence. Unordered matches do not qualify.
**Lottery Launch Timing**
The Qzino Lottery will not start immediately. During the initial phase, the system focuses on accumulating the prize pool through ongoing NGR contributions. Once the prize pool reaches a level that ensures meaningful rewards and a strong user experience, the Qzino team will announce the official start of weekly draws in advance.
---
# 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://docs.qzino.com/getting-started/lottery.md?ask=&goal=
```
`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.