> For the complete documentation index, see [llms.txt](https://docs.stonksnipebot.best/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stonksnipebot.best/security-and-rules/risks-and-faq.md). # Risks and FAQ ### Risk warning No authentication method guarantees project legitimacy, contract safety, execution, or profit. Treat every new token trade as a potential total loss. Latency, liquidity changes, token taxes, hooks, external controllers, MEV, reverts, and failed broadcasts remain possible. A transaction can fail or execute at an unfavorable price. ### Common questions #### Does a safe CA guarantee a trade? No. The service also needs a ready verified route, a valid quote, simulation, gas, balance, signing, broadcast, and receipt confirmation. #### Does deployment mean trading is ready? No. Production Launcher/V3 routes become eligible only after official frontend and on-chain evidence confirms them. #### Can the service guarantee a project is legitimate? No. Verification reduces uncertainty. It cannot eliminate contract, market, or issuer risk. #### Where should I manage wallets? Use private chat only. Group alerts do not expose wallet actions or other users’ trade results. --- # 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.stonksnipebot.best/security-and-rules/risks-and-faq.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.