> For the complete documentation index, see [llms.txt](https://trenchexchange.gitbook.io/trench-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://trenchexchange.gitbook.io/trench-docs/account-safety/known-risks.md). # Known Risks #### Volatility Crypto markets move quickly. * Prices can change rapidly * Opportunities and risks both appear fast *** #### Slippage Trades may execute at slightly different prices than expected. * More common during fast market movement * Can increase with larger trade sizes *** #### Liquidity Some tokens may have limited liquidity. * Large orders can impact price * Entry and exit may not always be smooth *** #### No Guarantee of Profit Data and signals are meant to assist, not predict. * Market outcomes are uncertain * All trading decisions are made by the user *** #### Security Principles * Verify transactions before signing * Avoid unknown links or approvals * Never share private keys --- # 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://trenchexchange.gitbook.io/trench-docs/account-safety/known-risks.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.