> 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-layer-1/overview/roadmap.md).

# Roadmap

Key milestones delivered to date, and what is planned next.

## Delivered

* **2022 · Founded.** Nexus begins research into zero-knowledge proof systems.
* **Sep 2022 · Seed round.** Led by Dragonfly.
* **May 2024 · Series A.** Co-led by Lightspeed and Pantera.
* **Q1 2026 · Testnet matching engine.** The Exchange matching engine goes live on testnet.
* **Jun 2026 · Exchange testnet.** The Nexus Exchange opens for trading on testnet.

## Upcoming

* **H2 2026 · Exchange (production).** Production launch of the Nexus Exchange for perpetual futures.
* **Next · Equities.** Equity perpetuals follow the launch markets. Commodities and FX are on the roadmap.

***

<sub>Forward-looking statement. Roadmap items, timelines, and dates are estimates only, subject to change without notice, and may differ materially from actual outcomes.</sub>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nexus.xyz/exchange-layer-1/overview/roadmap.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.