> For the complete documentation index, see [llms.txt](https://cashhand.gitbook.io/white_paper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cashhand.gitbook.io/white_paper/staking.md). # Staking Earn CashHand through CashHand CashHand Staking serves as an incentivization mechanism for deposits in the CashHand Token, providing remuneration to investors based on the duration of their commitment. In essence, it operates similarly to a direct treasury, serving as a passive income application disbursed in CashHand Tokens. Investors maintain their investments securely locked within the staking pool while receiving corresponding profitability, which is available for withdrawal at the investor's discretion.
CashHand presents two Staking Pools, each offering distinct time frames and associated percentage returns. Investors have the flexibility to opt for a lock-in period of either 30 or 90 days, with varying rates contingent upon the selected option. Notably, rewards are accessible for withdrawal at any juncture according to the investor's preference. Given its BEP20 Token nature, Staking CashHand aligns with the block time of the Binance Smart Chain network, operating on a schedule of 28,800 blocks per day. Specifically, the reward distribution for staking periods is outlined as follows: * For a 30-day commitment: 0.025 CashHand per block, distributed proportionally among all participants during the block period. * For a 90-day commitment: 0.1 CashHand per block, similarly shared among all participants throughout the designated block period. \ Stake CashHand here:\ \ --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://cashhand.gitbook.io/white_paper/staking.md?ask=&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 `automate deployments from our CI pipeline` 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.