> 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/using-tracker-with-research-and-trading.md).

# Using Tracker with Research and Trading

**Tracker notices the move. Research checks the move. Trading places the trade. Skip steps at your own risk.**

Tracker is a starting point — wallet and Twitter/X signals that flag *something is happening*. Whether something is worth acting on is a Research question, and whether to place a trade is a Trading question. This page is the bridge between the three.

{% hint style="success" %}
**Three-screen rhythm**

Tracker → Research → Trading. Acting straight from a tracker alert is how stale signals turn into bad trades.
{% endhint %}

## From Wallet Activity to Research

When Wallet Tracker shows an interesting move:

1. **Read the row.** Wallet, token, amount, transaction reference.
2. **Open the token context** when the row exposes it.
3. **Review Research data** — market cap, live liquidity, transaction count, volume, audit signals.
4. **Check timing.** Is the activity still relevant, or has the market already moved past it?

**Do not copy a wallet action without checking current liquidity and token risk.** A whale that bought 30 minutes ago into a thin pool may have already exited; the same trade for you starts a fresh slippage curve.

## From Twitter/X Activity to Research

When Twitter/X Tracker surfaces a post or alert:

1. **Review the account and content.** Who said what?
2. **Check for token identification.** Is a ticker, contract, or pair clearly named? Vague hype isn't a signal.
3. **Verify in Research / token page.** Find the on-chain identity that matches the tweet.
4. **Review audit signals and liquidity** before considering a trade.

Social posts can be **early signals** — they can also be **promotional, incomplete, or wrong**. Treat them as the start of an investigation, not its conclusion.

## From Tracker to Trading

Before placing a trade based on Tracker activity:

* **Confirm the token address** — ticker is not enough.
* **Review liquidity and market cap** on the [token page](/graphdex-docs/trading/token-page.md).
* **Check audit signals** — see [Audit Signals](/graphdex-docs/research/audit-signals.md).
* **Confirm wallet balance.**
* **Review Trading Settings** — current slippage, priority, bribe profile.
* **Understand the execution levers** — [Priority Fee](/graphdex-docs/trading/priority-fee.md), [Validator Bribe](/graphdex-docs/trading/validator-bribe.md), [Slippage](/graphdex-docs/trading/slippage.md).

Tracker helps you **notice** activity. Trading decisions still require **your own review**.

## A Common Anti-Pattern

The single fastest path to bad trades:

> *Tweet → Quick Buy → wonder what just happened.*

Avoid it. The five additional seconds for Research and the trading checklist are the cheapest insurance available.

## 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/m1zZKHwtJxpa0f4cJYJD"><strong>Wallet Tracker</strong></a></td><td>The on-chain side of the input.</td><td><a href="/files/AnuIRgx3Ju4HdXa1cEG3">/files/AnuIRgx3Ju4HdXa1cEG3</a></td></tr><tr><td><a href="/pages/2PlFU4Pt3OKOoBaNMfAK"><strong>Twitter/X Tracker</strong></a></td><td>The social side of the input.</td><td><a href="/files/OVXlon60XqRGRA8pZwho">/files/OVXlon60XqRGRA8pZwho</a></td></tr><tr><td><a href="/pages/OMivUziEbyoA9jTgesYW"><strong>Risk of Fast Execution</strong></a></td><td>What goes wrong when the rhythm is skipped.</td><td><a href="/files/PvwZariSc5lrxmA3uidW">/files/PvwZariSc5lrxmA3uidW</a></td></tr></tbody></table>

{% hint style="info" %}
Tracker is one input among many. Pulse signals, Research tables, audit panels, and your own watchlist all feed the same decision pipeline.
{% endhint %}

## FAQs

<details>

<summary>How long should I spend on Tracker → Research before deciding?</summary>

60–120 seconds for routine alerts. Faster only if you already know the token from prior research; longer if the signal is unusual or the token is new.

</details>

<details>

<summary>Can I configure Tracker to auto-trade?</summary>

No — Tracker is a monitoring surface, not an execution surface. Trades go through the Trading panel where you review and confirm them.

</details>

<details>

<summary>What if Research contradicts the Tracker signal?</summary>

Trust Research. Tracker is fast; Research is thorough. If a whale buy is contradicted by weak liquidity and concerning audit signals, the whale may know something — or may be wrong.

</details>

<details>

<summary>Should I size trades the same when sourced from Tracker vs. my own research?</summary>

Position-sizing is personal, but most traders size more conservatively when the trade is sourced from an external signal they're verifying mid-flight.

</details>

<details>

<summary>How fresh do Tracker signals need to be to be actionable?</summary>

Depends on the token's volatility and the signal type. Whale buys on thin pools age quickly; broader social signals on liquid pairs age more slowly. When in doubt, treat anything older than a few minutes as informational, not actionable.

</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/using-tracker-with-research-and-trading.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.