> For the complete documentation index, see [llms.txt](https://clown-town.gitbook.io/clown-town/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://clown-town.gitbook.io/clown-town/casino/jakpot.md). # Jakpot ## HOW IT WORKS The Clown Town Jakpot takes both $CLOWNS and ETH from the user when they buy a ticket. Each ticket gets the user a chance to win 33% of the total prize pot. The remaining 2/3rds of the pot goes to liquidity and marketing expenses. Each time the user transfers $CLOWNS to the contract, the gambling token functionality runs and a potential winner is drawn for the Token Jackpot! The total number of tickets for the first lottery will be 50 tickets. Once 50 tickets have been bought, the contract automatically draws a winner and transfers the ETH to their address. As Clown Town grows, the contract size will increase along with larger prizes and even more transfers. All payout functionality is done via the smart contract and the dev team has no control or weight on the outcome of the lottery. Like any lottery, the more tickets you hold, the more chances you have to win. The CLOWNS sent to the Jakpot pool will be reflected back to the CLOWNS holders and also for liquidity management. --- # 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: ``` GET https://clown-town.gitbook.io/clown-town/casino/jakpot.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.