# Staking {% hint style="info" %} Step-by-step guide how to Staking PULSE: {% endhint %} | Staking duration | Rewards | | ---------------- | ------- | | 14 days | 2,5% | | 1 month | 5,5% | | 3 months | 19% | | 6 months | 45% | | 1 year | 120% | \ The principle of staking is often compared to a bank deposit, when the user puts money in an account for a certain period of time. The more money in the account, the higher the profit. Theoretically, making money on PoS algorithm is simple: it is enough to synchronize your wallet with the network, keep the coins and don’t turn the wallet off from the network. After a certain time, the validator will receive new coins as a reward for confirming the block. Technically, this is easier than buying expensive mining equipment, setting up devices, renting space for them and constantly thinking about their payback. Pulse has simplified this process! Staking has become even more convenient and comfortable. User doesn’t need to worry if something happens with connection to the wallet or the gadget breaks down. All you need to do is send PULSE to the staking contract. The reward will be received regardless of whether the wallet is connected or the computer is turned off. Another fundamental type of staking with PULSE is so called Strong Hand Staking, that provides price stability to PULSE by passing fees in strong hands — to PVault. Both of these options will benefit users and the entire PULSE ecosystem. The more stakers lock their tokens, the higher the price will be, as well as the higher the reward. A locked position keeps the entire ecosystem stable, as well as your nerves when the price changes. --- # Agent Instructions: 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://pulsedefiltd.gitbook.io/pulse-docs/staking.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.