> For the complete documentation index, see [llms.txt](https://whitepaper.solotto.top/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.solotto.top/introduction.md).

# Introduction

**SOLOTTO** is a decentralized, automated lottery protocol built on the Solana blockchain, designed to bring fast-paced, transparent, and rewarding draws to crypto users around the world. With lottery draws happening every 15 minutes—alongside daily, weekly, and monthly prizes—SOLOTTO redefines what it means to win in web3.

The platform’s native token, **$SLOT**, powers the ecosystem and will officially launch on **Monday, June 23 at 7PM UTC**.

Each prize distribution follows a unique split: **50% is paid out in SOL**, while **the other 50% is used to buy $SLOT on a decentralized exchange (DEX)** and is then sent directly to the winner. This mechanism ensures not only instant rewards but also consistent buy pressure on $SLOT, aligning token growth with platform engagement.

With no middlemen, verifiable fairness using on-chain VRF, and a sleek, always-on interface showing live winners and leaderboard data, SOLOTTO delivers a new standard in decentralized gaming—transparent, fair, and exciting every 15 minutes.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://whitepaper.solotto.top/introduction.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 `build a script that syncs our docs to a CMS` 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.