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

# Roadmap

**Q1 2025**

* Mint A7A5 on **Tron and Ethereum** ✅
* **DEXes.** Listings to establish A7A5 as a highly liquid asset ✅

**Q2-4 2025**

* [**Reserves audit**](https://a7a5.io/transparency) by Kreston (a global audit firm in 100+ countries) ✅
* **Liquidity pool** [**on Tron**](https://a7a5.io/trade_and_earn?chain=tron) for A7A5 <> USDT swaps ✅
* **On & Off-Ramp Solutions** to make it easier for individuals and businesses to buy, sell, and use A7A5 seamlessly  ✅
* **Lintings on CEXes.** CEXes will also serve as bridges between A7A5 on Tron and Ethereum
* **Lending & borrowing** integrations on DeFi platforms
* Enabling users to earn through **classic carry trade** with stablecoin pairs
* **New Partnerships & Integrations** to enhance access to A7A5 for users across various countries and fiat currencies
* **Institutional & Retail Use Cases** to develop new opportunities for both individual and corporate users to utilize A7A5 in everyday transactions and financial operations

Stay tuned for updates—more details 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 by asking a question.

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

```
GET https://docs-en.a7a5.tech/introduction-to-a7a5/roadmap.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.
