> For the complete documentation index, see [llms.txt](https://docs.mayaprotocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mayaprotocol.com/white-paper/readme-1-1.md).

# Maya Whitepaper 2.0

A next-gen cross chain DEX.

{% hint style="warning" %}
**Disclaimer:** *This document has been revised from its original version to reflect new ideas and certain recent economic adjustments at the time it was created. These tweaks have been previously announced and set to consideration with the Maya Protocol community in our official* [*Discord*](https://discord.gg/xZjdXBbu7V) *server. **It is important to note that this document currently serves historical purposes and that some information included in it maybe outdated.***
{% endhint %}

{% hint style="info" %}
Do you prefer downloading or printing? You can use this link to get the [Whitepaper as a PDF](https://assets.website-files.com/62a14669b65c6aeed054f32e/632358a7a50bee6b8298c1cb_MAYA%20PROTOCOL%20WHITE%20PAPER.pdf). Just remember this is the most updated version until November 2022. We will update it soon with the new adjustments.
{% 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 by asking a question.

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

```
GET https://docs.mayaprotocol.com/white-paper/readme-1-1.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.