> For the complete documentation index, see [llms.txt](https://jexchange.gitbook.io/english/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jexchange.gitbook.io/english/raffles.md). # Raffles The “Raffles” interface allows users to create permissionless lotteries. A lottery meets the following requirements: * A start date and an end date * A token identifier * One price per ticket * Number of winning tickets On each ticket, a % of token amount is burned, another % is used as raffle owner royalties, another % is used as JEX platform fee, the remaining feeds the prize pool. The breakdown is detailed below. The draw is carried out by a smart contract, the code of which is open source. ## Ticket payment breakdown (JEX protocol fee amount) = (ticket price) \* (% JEX protocol fee) (net ticket price) = (ticket price) - (JEX protocol fee amount) (burned amount) = (net ticket price) \* (% burn) (owner royalties) = (net ticket price) \* (% owner royalties) (prize pool) = (net ticket price) - (burned amount) - (owner royalties) --- # 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://jexchange.gitbook.io/english/raffles.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.