# The ExoniumDEX format

As mentioned in previous sections, the success of Ethereum-based DEXes such as UNISWAP and PancakeSwap cannot be understated. The millions of users have clearly indicated their preference of a simple, unified platform that links directly with their Web3.0 compliant wallets such as Metamask and Imtoken.

In this spirit of commercial viability and in order to leverage on ongoing network effects. The ExoniumDEX team naturally gravitated to a similar model of DEX, and will develop on the existing AMM DEX model.

This means that ExoniumDEX will share the concepts of swap mechanisms, fee structure and liquidity pools that has made UNISWAP such a commercial success. At the beginning, ExoniumDEX will only support BSC tokens, and will extend this to all major blockchains followed by any public, open-source blockchain available. This will flow in tandem with the release of ExoniumOracle and ExoniumBridge.

| Date           | Q3 2021                  | Q1 2022          | Q2 2022          | Q3 2022                |
| -------------- | ------------------------ | ---------------- | ---------------- | ---------------------- |
| Product        | <p>tEXO</p><p>Launch</p> | Exonium Bridge   | Exonium Oracle   | Full System Launch     |
| Supportability | BSC/POLY                 | Major Blockchain | Major Blockchain | ALL Public Blockchains |

Fig 3: Deployability Timeline for ExoniumDEX fleet of products and supportability \ <br>


---

# Agent Instructions: 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:

```
GET https://texo.gitbook.io/exoniumdex/exonium-mainnet/the-exoniumdex-format.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.