> For the complete documentation index, see [llms.txt](https://winbit-casino-1.gitbook.io/winbit-casino/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://winbit-casino-1.gitbook.io/winbit-casino/how-to/staking.md). # Staking 1\) Create a Winbit account 2\) Hold $WIN 3\) For additional rewards, lock-up $WIN 4\) Done. For the full details on how Winbit Casino implements the staking and profit share model, check out [Staking & Profit sharing](/winbit-casino/platform/rewards-and-incentives/staking-and-profit-sharing.md) #### Important reminders All revenue is paid out in $USDT. Revenue is shared on a weekly basis The share is distributed in accordance with the holdings. More $WIN will result in a larger piece of the pie. There is no minimum $WIN amount required in order to start earning passive income. To see the model of revenue share check out [Broken mention](broken://pages/5F5NwNMcc2TRUlcE38qP) --- # 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://winbit-casino-1.gitbook.io/winbit-casino/how-to/staking.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.