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

# Welcome to 0xLotto Documentation

Trade risky shitcoins for real wins at 0xLotto! Better odds, true excitement.

{% hint style="info" %}
**GitBook tip:** your product docs aren't just a reference of all your features! use them to encourage folks to perform certain actions and discover the value in your product.
{% endhint %}

{% embed url="<https://youtu.be/vD5qgBcsOns>" %}

Experience the magic of winning with 0xLotto! Our ***draws are powered by*** a combination of  accumulated taxes on $LOTTO tokens and ticket sales. All while providing you a chance to stake $LOTTO and earn a 70% revenue share. With Chainlink's VRF ensuring fair draws, you can dive into an exhilarating world of opportunity and excitement. Delve into our unique ecosystem, and discover the thrill of genuine gaming rewards! 🎰🔢🔥🚀


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://0xlotto.gitbook.io/documentation/welcome-to-0xlotto-documentation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.