> For the complete documentation index, see [llms.txt](https://raffeldotfun.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://raffeldotfun.gitbook.io/docs/overview/intro.md). # Intro ## Welcome to raffel.fun raffel.fun is a fair, fun savings game on the Solana blockchain. Deposit USDC, earn tickets towards the next raffle to win Bitcoin and collect points — all while keeping your money safe. It’s a simple way to save with a chance to win big! {% hint style="info" %} Save, Play, and Win! — Without risk of loosing. {% endhint %} ## How it works? 1. **Deposit USDC**: Connect your Solana wallet and deposit at least $69 USDC. 2. **Earn Tickets**: Get 1 ticket per day for every $10 deposited, starting after 24 hours. 3. **Enter Raffles**: All tickets earned join automatically the next raffle for a chance to win Bitcoin. 4. **Keep Saving**: Your USDC stays safe, win or lose, keep earning tickets or withdraw anytime. --- # 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://raffeldotfun.gitbook.io/docs/overview/intro.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.