> 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/aztec-chain-and-usdaztec-token.md).
# Aztec Chain & $AZTEC token
A new ecosystem for $CACAO
Aztec is a powerful demonstration of the high potential of the Maya Protocol’s design and how it can expand horizontally to offer different complementary products. We are excited about the endless possibilities of combining Maya’s liquidity black hole properties with Aztec’s Smart Contracts and economic capabilities!
### ELI5
1\. Smart Contracts are necessary to add complexity and dynamism to flourishing crypto economies because they provide builders and developers with the flexibility to create and experiment. Smart Contracts will provide an avenue for Maya derivatives —i.e., Synths— to find use cases.
2\. Aztec is a fork of Cosmos. We decided to do this based on several factors like mature infrastructure and extensive Smart Contract development.
3\. Aztec will take a role in the algorithmic stablecoin quest, but it will not have a “one mechanism for all” approach. Instead, it will work with a full suite of different tokens that coexist, complement each other and offer different types of risks. Our algorithmic stablecoins will be turned off at launch, giving us time to finish with the economic design and to run the appropriate bounties’ programs, etc. Maya and Aztec will never subsidize yield to inflate demand for any of their own stablecoins or derivatives.
\\
---
# 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/aztec-chain-and-usdaztec-token.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.
