> For the complete documentation index, see [llms.txt](https://docs.nexus.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexus.xyz/exchange/architecture.md). # Architecture The Nexus Exchange runs a high-performance order book and matching engine, with execution settled on-chain and independently verifiable. It is live on Nexus Testnet today as a development preview; the production launch follows in a later release. ### Nexus Exchange components * **Execution** — two synchronized execution environments process all transactions and state transitions: * **NexusCore** — the high-performance engine that hosts *enshrined co-processors* for specialized financial operations, with deterministic execution at 200 ms block intervals. * **NexusEVM** — an Ethereum-compatible virtual machine providing general-purpose programmability, composability, and full EVM tooling. * **Consensus** — **NexusBFT**, a Byzantine Fault Tolerant protocol that finalizes dual-execution blocks, coordinates validators, and manages the on-chain registry of co-processors. * **Verification** — the **Compute Network** progressively proves execution, so anyone can verify it independently without trusting the operator. Together these let developers build and access institutional-grade financial infrastructure on-chain — with 200 ms block intervals, shared native liquidity, and verifiable execution — bringing the speed, depth, and reliability of traditional markets into an open, composable blockchain 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.nexus.xyz/exchange/architecture.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.