> For the complete documentation index, see [llms.txt](https://docs.jvault.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jvault.xyz/staking-v1-deprecated/for-stakers/jvault-warranties.md). # JVault warranties The entire staking process is **completely secure and decentralised** in terms of asset ownership: at all stages of staking, your tokens belong only to you, and no one can use them. The service is based on smart contracts, so even if the site stops working, you will still be able to fully utilise all the staking pools: all you need to do is send certain messages to the blockchain. You can explore the open source code of all smart contracts and learn how they work on the [project's GitHub](https://github.com/orgs/JVault-app/repositories). However, due to decentralisation, [JVault ](https://jvault.xyz/stake)cannot be held responsible for the actions of projects hosted on the platform. [JVault](https://jvault.xyz/stake) does not encourage users to invest in any digital assets, and therefore is not liable for any losses related to changes in token rates. We recommend seeking specialist advice before investing your money in cryptocurrency, as this area involves high risks. You can read more about the terms of use of the platform [here](https://jvault.xyz/static/tos.pdf). --- # 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://docs.jvault.xyz/staking-v1-deprecated/for-stakers/jvault-warranties.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.