> For the complete documentation index, see [llms.txt](https://whitepaper.myrenegade.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.myrenegade.net/the-challenges-currently-facing-cryptocurrency-exchanges/trading-fees.md). # Trading fees As a result of the present deadlock, substantial fees continue to be charged to both parties in cryptocurrency exchange markets. When a particular level is reached, trading becomes prohibitively expensive. Renegade believes that a blockchain-based, well-automated exchange should be minimal in cost and accessible to anyone. Once built, the entire infrastructure is constantly available. Of course, upgrades and new functionalities are crucial, but the capacity to deliver a comprehensive range of services is the most significant component. This implies that the costs of these particular functions must stay minimal. --- # 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://whitepaper.myrenegade.net/the-challenges-currently-facing-cryptocurrency-exchanges/trading-fees.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.