> 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/usdmaya-token/philosophical-perspective-mt.md).
# Philosophical perspective MT
Having two tokens is directly related to our decision to launch using a Liquidity Auction and to how we want our community to be as equitable, as big, and as widespread as possible.
$MAYA’s design has been carefully planned to prevent incentives’ misalignments for the insiders holding them, and they allowed us to financially bootstrap our project in its earliest stages without having to recur to any pre-sales of $CACAO, which we really wanted to avoid.
Both tokens can be freely traded, and they offer their respective holders the right to earn a percentage of the fees generated inside our protocol, although with different approaches, as described below.
**On Governance.** To achieve a high level of decentralization Maya has minimal governance, similar to THORChain. This aspect is directly related to the security of the protocol so that the nodes are the ones who carry out the governance and ensure that all incentives are granted through code. In the specific case of $MAYA tokens, they don’t give any governance rights to their holders, or any other right whatsoever.
You can see more about this topic [here](https://docs.mayaprotocol.org/how-it-works/governance).
---
# 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/usdmaya-token/philosophical-perspective-mt.md?ask=&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.
