> For the complete documentation index, see [llms.txt](https://fordex.gitbook.io/fordex/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fordex.gitbook.io/fordex/roadmaps/phase-2.md).

# Phase 2

## Phase 2 — Expansion (Q4 2025)

This phase expands Fordex from a market tracker into a **fully interactive trading hub**.

#### **Milestones**

* ⚡ **Trade Terminal V1** → One-click buy/sell, multi-router aggregation, gas estimator.
* 🤖 **AI Screening V1** → Natural language queries and AI-based risk scoring.
* 🛡️ **Honeypot Simulation** → Dry-run buy/sell, slippage guard recommendations.
* 💼 **Portfolio Tracking** → Wallet connect, balance view, basic PnL with CSV import.
* 📢 **Alerts & Bots Upgrade** → Advanced alerts (whale Tx, rug signals), integration with Telegram/Discord bots.

#### **Goal**

Transform Fordex into a **one-stop platform** where users can screen, assess risk, and trade seamlessly.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://fordex.gitbook.io/fordex/roadmaps/phase-2.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.