> For the complete documentation index, see [llms.txt](https://zenko.gitbook.io/zenko-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zenko.gitbook.io/zenko-whitepaper/zenko-exchange/overview.md). # Overview The **Zenko Exchange** is a non-custodial, performance-grade crypto trading platform that combines the efficiency of centralized order execution with the security and transparency of decentralized custody. It is engineered to operate as a **hybrid CEX/DEX model**, where all user funds remain in self-custody and trades are settled through smart contract mechanisms. Traditional exchanges act as custodians, introducing central points of failure, opaque balance sheets, and custodial risks. Zenko removes these vectors by separating **execution from custody**, giving users full control of their private keys while still enabling fast, low-latency trading. Key design principles of the Zenko Exchange: * **Self-Custody by Default:** Users retain full control over their assets at all times. No funds are held by the exchange — all trades are routed through audited smart contracts or MPC-based signature flows. * **High-Performance Matching Engine:** A centralized matching layer ensures millisecond-level order execution, deterministic matching, and support for advanced order types. * **Composable Trading Infrastructure:** Built with modular APIs and SDKs for developer integrations, trading bots, and programmatic strategy execution. * **Revenue Alignment with the Ecosystem:** All exchange fees (maker/taker, listing, premium tools) are programmatically directed to community-aligned systems — including token buybacks, burns, staking rewards, and treasury reserves. * **Transparency and Auditability:** Core logic governing fees, custody, and protocol revenue flows is embedded in public smart contracts and tracked via on-chain dashboards. --- # 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://zenko.gitbook.io/zenko-whitepaper/zenko-exchange/overview.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.