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

# Tracker Overview

**Tracker is the watchlist side of GraphDex — follow on-chain wallets and X/Twitter accounts, and pipe every signal straight into Research and Trading.**

{% hint style="info" %}
On the Polygon (Predictions) side of GraphDex, this section has a parallel — see [Predictions side](/graphdex-docs/tracker-predictions/tracker-overview.md).
{% endhint %}

<div align="center"><figure><img src="/files/2sEqNCDF4c3fGMIOn9g8" alt="Tracker — wallets and X/Twitter together"><figcaption><p>Tracker — wallet and social activity in one watchlist.</p></figcaption></figure></div>

Tracker turns "interesting wallets" and "interesting accounts" into a feed. Add an on-chain wallet to **Wallet Tracker** and you see its trades the moment they happen; add an X handle to **Twitter Tracker** and you see the tickers it mentions the moment they surface. Both surfaces share one notification stream and one entry point from the bottom toolbar.

The point of Tracker isn't observation for its own sake — it's a workflow input. Every tracker hit is one click away from opening the token in **Research** for a deeper read, or jumping into the token page in **Trading** for the order panel. Cross-reference a tracker hit with **Pulse** and you have wallet movement, social attention, and live token activity stacked on the same selection.

Tracker is a signal layer, not a safety check. Activity surfaced here is information — not a guarantee that a token is safe, liquid, or worth trading.

{% hint style="success" %}
**Watch wallets and accounts, act on the signal**

Add a wallet or X handle, get a notification when it moves, jump straight to Research or Trading on the related token.
{% endhint %}

## The Two Tracker Lanes

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><a href="/pages/m1zZKHwtJxpa0f4cJYJD"><strong>Wallet Tracker</strong></a></td><td>Follow on-chain wallets and get notified the moment they trade.</td><td><a href="/files/BWULSHt4tqY255s7X9t1">/files/BWULSHt4tqY255s7X9t1</a></td></tr><tr><td><a href="/pages/2PlFU4Pt3OKOoBaNMfAK"><strong>Twitter / X Tracker</strong></a></td><td>Follow X accounts and surface tickers the second they're mentioned.</td><td><a href="/files/2sEqNCDF4c3fGMIOn9g8">/files/2sEqNCDF4c3fGMIOn9g8</a></td></tr><tr><td><a href="/pages/AVlBX9c7pQQjTospVQGB"><strong>Notifications</strong></a></td><td>The unified alert stream that fires for every tracker hit.</td><td></td></tr></tbody></table>

## WALLET TRACKER

<figure><img src="/files/BWULSHt4tqY255s7X9t1" alt="Wallet Tracker — followed on-chain wallets"><figcaption></figcaption></figure>

Wallet Tracker watches the addresses you care about — funds, smart-money wallets, your own secondary wallets — and surfaces their trades in real time.

* Follow any on-chain wallet by address.
* See trade events as they're confirmed on-chain.
* Notification fires the moment a tracked wallet moves size.
* One click on a tracker hit opens the related token in Research or Trading.
* Import and export flows let you bulk-manage the watchlist.

## TWITTER / X TRACKER

<figure><img src="/files/2sEqNCDF4c3fGMIOn9g8" alt="Twitter / X Tracker — followed accounts"><figcaption></figcaption></figure>

Twitter Tracker is the social half of the watchlist. It scans posts from followed accounts for tickers and routes the hit back into the terminal.

* Follow X / Twitter accounts by handle.
* Surface tickers the second they're mentioned in a post.
* Stack social hits next to wallet hits on the same notification stream.
* Open any mentioned token straight in Research or Trading.

## NOTIFICATIONS AND ALERTS

Both lanes feed the same notification surface. Alerts persist on the alert state view, so a missed hit doesn't disappear.

* Single stream covers wallet trades and social mentions.
* Notification settings live on the Tracker views.
* Alert state and settings views are shared between Wallet and Twitter Tracker.
* Tracker views may require a signed-in account — if the route redirects, sign in and return.

## How Tracker Plugs into the Workflow

Tracker is the input. Research, Trading, and Pulse are the next steps. The recommended cadence:

1. Watch wallet or X / Twitter activity.
2. Open the related token or account context.
3. Use **Research** to review market data and audit signals.
4. Use **Trading** only after checking liquidity, wallet state, and Trading Settings.

## More to Explore

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><a href="/pages/XJTcByJsbupiZnUUjdb4"><strong>Tracker × Research × Trading</strong></a></td><td>The cadence of moving from a tracker hit to a confirmed trade.</td><td></td></tr><tr><td><a href="/pages/aBbtiUPZOLY1d6Cro0Xn"><strong>Pulse</strong></a></td><td>Cross-confirm tracker hits with live token activity lanes.</td><td></td></tr><tr><td><a href="/pages/u7WCycdkf5le4FRMndCn"><strong>Research</strong></a></td><td>Where to go right after a tracker hit for a deeper market read.</td><td></td></tr><tr><td><a href="/pages/0V5np5mUGRe5aAyqgLVm"><strong>Trading</strong></a></td><td>The execution layer that consumes tracker hits.</td><td></td></tr><tr><td><a href="/pages/ivf2Yli81NUiF5vCsxey"><strong>Audit Signals</strong></a></td><td>Risk markers to apply before trading any tracker-surfaced token.</td><td></td></tr><tr><td><a href="/pages/OMivUziEbyoA9jTgesYW"><strong>Risk of Fast Execution</strong></a></td><td>Reading a tracker hit fast doesn't mean trading it fast — read this first.</td><td></td></tr></tbody></table>

{% hint style="info" %}
Tracker surfaces activity and alerts. It does not confirm that a token is safe or that a trade should be placed — always confirm in Research and on the Token Page before sending an order.
{% endhint %}

## FAQs

<details>

<summary>What can I track?</summary>

* **On-chain wallets** by address — Wallet Tracker.
* **X / Twitter accounts** by handle — Twitter Tracker.

Both feed a shared notification stream.

</details>

<details>

<summary>Where does Tracker live in the UI?</summary>

In the main navigation as **Tracker**, plus direct entries on the bottom toolbar for **Wallet Tracker** and **Twitter Tracker**.

</details>

<details>

<summary>What happens when a tracked wallet trades or a tracked account posts?</summary>

A notification fires on the Tracker alert stream, and the hit becomes one-click clickable into the related token's Research or Trading page.

</details>

<details>

<summary>Do I need to sign in to use Tracker?</summary>

Some Tracker views require a signed-in account. If a route redirects you, sign in and re-open Tracker.

</details>

<details>

<summary>Can I move tracked items in bulk?</summary>

Yes — Tracker has import and export flows so you can bulk-manage watchlists rather than adding entries one at a time.

</details>

<details>

<summary>Is a tracker hit a trade signal?</summary>

No. Tracker is monitoring, not advice. A hit is an input — always confirm in [Research](/graphdex-docs/research/research-overview.md) and the [Token Page](/graphdex-docs/trading/token-page.md), and review your Trading Settings before placing an order.

</details>


---

# 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://graphdex-1.gitbook.io/graphdex-docs/tracker/tracker-overview.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.