> For the complete documentation index, see [llms.txt](https://rollx-docs.gitbook.io/rollx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rollx-docs.gitbook.io/rollx/rollx-v2.md).

# RollX V2

RollX v2: A TEE-Enabled PerpDEX Appchain for the Base Ecosystem

We’re excited to share the next chapter of RollX on Base: RollX v2, a high-performance perpetual futures exchange built as a TEE-enabled Layer-3 (L3) appchain on top of Base.

The goal is simple to say but hard to build:

CEX-like speed and risk management, with DeFi-grade self-custody and composability — all anchored on Base.

Here is a technical but accessible overview of what RollX v2 is, how it uses Base’s strengths (asset composability, DeFi landscape, TEEs, appchains), and what it unlocks for traders, builders, and the broader Base community. For full details, you can always dive into the technical whitepaper (coming soon).


---

# 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://rollx-docs.gitbook.io/rollx/rollx-v2.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.