> For the complete documentation index, see [llms.txt](https://docs.quantpad.company/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.quantpad.company/reference/safety.md). # Safety Custody, risk and the third parties every Quant Pad coin depends on. ## Your keys stay with you Quant Pad never holds your keys. Every action is a transaction you review and sign in your own wallet. Quant Pad cannot reverse transactions. ## Risks {% hint style="danger" %} Memecoins are extremely volatile and most lose all value. Tokens launched on Quant Pad have no intrinsic value and no promise of returns. You can lose everything you spend. {% endhint %} * The Quantum Hooks program has not yet been independently audited. Smart contracts can contain bugs. * Buybacks are market orders and can be front-run. Each burn is capped in size to limit that. ## Third parties Coins are created and traded through Meteora's Dynamic Bonding Curve and DAMM v2, which are operated by third parties with their own fees, rules and admin powers. * Meteora can upgrade its programs, and its operators can change or pause a migrated pool. * Quantum Hooks depend on Meteora continuing to pay creator fees to the well. See [Guarantees and risks](/quantum-hooks/guarantees-and-risks.md) for what the Quantum Hooks program does and doesn't guarantee. --- # 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://docs.quantpad.company/reference/safety.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.