> For the complete documentation index, see [llms.txt](https://docs.zkex.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zkex.com/overview/trading.md). # Trading ## Trading Types * Limit Order (available) * Market Order (available) * Stop Market * Stop Limit * Trailing Stop * Take Profit * Take Profit Limit ## Trading Pairs We plan to go live with a small number of pairs, with the potential of hundreds being eventually available. ## Self Trade At ZKEX, a "Self Trade" is identified when the creator (maker) and the receiver (taker) of the order are the same address. In such instances, ZKEX refrains from pushing the transaction to Layer 2, thereby not incurring any transaction fees. The implementation of this feature is aimed at ensuring the fairness and transparency of transactions. Since a self-trade does not lead to any actual change in user assets, we opt not to process it to prevent potential market manipulation and unnecessary network congestion. Furthermore, we would like to emphasize that ZKEX only levies fees on genuinely effective transactions, a measure designed to maintain and enhance the overall health and stability of the trading environment. --- # 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.zkex.com/overview/trading.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.