# 8. Roadmap

<figure><img src="/files/FziQCeUDBvRc5EUNxxPb" alt=""><figcaption></figcaption></figure>

**Phase 1 - Project Conception**

* Research and planning focused on the TON blockchain.
* Establishing initial partnerships and outlining the project's vision.

**Phase 2 - Presale and Token Launch**

* Launch the ELX presale and list the tokens for selected exchanges.
* Develop the mining app and initiate marketing campaigns.

**Phase 3 - Platform Development**

* Develop the DEX, staking platform, and portfolio tracker.
* Conduct initial user testing to gather feedback and optimize the platform.

**Phase 4 - DEX & Staking dApp Launch**

* Beta launch of the DEX and introduction of initial trading pairs.
* Launch staking options for ELX tokens and improve AMM with dynamic fees.

**Phase 5 - Bridge Integration & Elluminex Academy**

* Deploy the cross-chain bridge for asset transfers.
* Launch Elluminex Academy to educate users on DeFi and blockchain.

**Phase 6 - Portfolio Tracker & Pre-Market Launch**

* Beta launch of the AI-powered portfolio tracker.
* Launch the pre-market platform for trading new TON tokens.

**Phase 7 - Mobile App Release & Gamification**

* Launch the mobile app for iOS and Android with full platform integration.
* Introduce gamification features to boost user engagement.

**Phase 8 - Ecosystem Expansion & Strategic Partnerships**

* Expand partnerships within the TON ecosystem.
* Launch ambassador programs and host hackathons.

**Phase 9 - Continued Development & Global Reach**

* Ongoing platform development and AI-powered analytics.
* Implement global expansion strategies to reach a wider audience.


---

# 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://elluminex.gitbook.io/elluminex-lite-paper/8.-roadmap.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.