> For the complete documentation index, see [llms.txt](https://doc.rocky.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.rocky.exchange/overview/roadmap.md).

# Roadmap

Rocky's phased path — from private perps to Canton's unified liquidity layer. Timelines are **indicative**; for a real-funds venue, correctness comes before speed.

## Phase 1 — Private Perps + Wallet *(now)*

Launch trading and capital entry points.

* **Privacy-preserving perpetuals** — order-book trading, market-maker API, risk & liquidation, Canton-native settlement.
* **Rocky Wallet** — self-custodial capital entry point.
* **Market maker onboarding.**
* **Canton ecosystem activity** — every trade, settlement, and margin event drives Canton usage.

## Phase 2 — RWA Liquidity

Extend privacy-preserving infrastructure to institutional assets.

* **RWA OTC** with private RFQ (request-for-quote) workflows.
* **Block trades** — large size without market impact or information leakage.
* **Collateral & settlement workflows** for tokenized real-world assets.

## Phase 3 — Unified Liquidity Layer

Become price and liquidity infrastructure for all of Canton.

* **Oracles & price discovery** — perp data, funding, basis, and OTC reference prices.
* **CCTP cross-chain liquidity** — route external stablecoin capital into Canton.
* **AI strategies** — funding-rate arbitrage, yield optimization, automated hedging.
* **24/7 price discovery** across Canton assets.

{% hint style="info" %}
These phases compound into a **liquidity flywheel**: capital flows into privacy-preserving perp trading, which generates fees, data, and Canton activity — attracting more liquidity over time.
{% endhint %}


---

# 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://doc.rocky.exchange/overview/roadmap.md?ask=<question>&goal=<endgoal>
```

`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.