> For the complete documentation index, see [llms.txt](https://docs.teranode.group/nchain-event/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.teranode.group/nchain-event/independent-records/use-cases/lucky-number-tickets.md).
# Lucky Number Tickets
A lucky number ticket operator wants to publish the randomly generated winning tickets for transparency and to avoid possible disputes.
1. The operator draws a lucky number winning ticket (picks a random number).
2. They write the ticket to the blockchain using nChain Event as unencoded records [**‡**](/nchain-event/overview/configuration-symbols.md), obtaining the record location which they publish.
3. Anyone with the location can read the winning ticket number and see when the draw was taken.
4. Any holder of a ticket can verify [**†**](/nchain-event/overview/configuration-symbols.md) whether theirs is the winning ticket.
**Benefits**
* The returned result is proof of what data an organisation submitted to the blockchain and when.
* Verifiable: The original data and time can be verified.
* Transparent: The Records are publicly accessible, and the result is readable from the blockchain.
* Irrefutable: A record of the data exists on the blockchain (tamperproof & cannot be repudiated).
* Trust and Fairness are established by using the blockchain, a decentralised independent arbiter.
{% hint style="info" %}
A Lucky Number demo application for nChain Event is available from the Product Suite Platform. See [here](https://ln.event.nchainplatform.com).
{% endhint %}
***Extended Lucky Number Scenario***
*The lucky number creator can create tickets by writing records to the blockchain, and using the resultant record location as the ticket number (since it is effectively a large random number).*
*Anyone can view their ticket on the blockchain and the set of potential winners can be fully transparent up to the time of the draw.*
*To make the draw, a ticket can be picked at random by using the low-order bits of the location of a written transaction as the random ticket selector.*
*The tickets, the winning ticket selection, the picker’s identifier and the winning ticket number can be written to the blockchain using nChain Event.*
*See* [*here*](/nchain-event/independent-records/tutorials/blockchain-unique-identifiers.md) *about persistent GUIDs and* [*here*](/nchain-event/linked-records/use-cases/random-prize-draw.md) *for more details of this extended screnario.*
{% content-ref url="/pages/CrPgi24sh3N5oBUFQ0JJ" %}
[Internet of Things (IoT) Data](/nchain-event/independent-records/use-cases/internet-of-things-iot-data.md)
{% endcontent-ref %}
---
# 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.teranode.group/nchain-event/independent-records/use-cases/lucky-number-tickets.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.