> For the complete documentation index, see [llms.txt](https://docs.trover.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trover.tech/safety-and-controls/fees-routes-and-risks.md). # fees, routes, and risks ## fees, routes, and risks ### fees trover currently charges no transaction fee. a 0.5% trover transaction fee is planned for the future. it should be shown before activation. separate costs may still apply: * source and destination network gas * token approvals * dex or liquidity-provider fees * bridge and relayer fees * price impact and slippage * wallet or provider charges ### routes and quotes quotes are time-sensitive estimates. a displayed route can expire or become invalid before signing or execution. the final result may change because of block conditions, gas, token taxes, liquidity, approvals, or provider behavior. trover validates route spenders and applies configured slippage bounds. it can reject thin liquidity, route divergence, unsupported chains, denied assets, or unverified contracts when the relevant controls are active. ### key risks * smart-contract bugs or malicious tokens * depegging or issuer risk * thin liquidity and large price impact * oracle, provider, rpc, or indexer failures * bridge or relayer failure * chain reorganization, congestion, or downtime * wallet compromise or unsafe approvals * regulatory or jurisdictional restrictions * ambiguous transaction status {% hint style="warning" %} don’t retry an action just because its status is delayed. first check the trover intent, wallet activity, and block explorer. a retry can create a second economic action. {% endhint %} --- # 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.trover.tech/safety-and-controls/fees-routes-and-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.