> 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/research-predictions/trends.md).

# Trends

**The biggest prediction markets right now — sorted by volume, the place to find where the money is.**

The **Trends** tab in Research re-sorts the table by total traded volume. The biggest markets — political races, championship winners, recurring crypto windows that have stacked up bids — rise to the top.

This is the view to keep open if you want depth: tight spreads, faster fills, and price action driven by real flow rather than guesses.

## What stands out on Trends

* High-volume long-window markets like *2026 FIFA World Cup Winner* or *Presidential Election Winner*. These often show **$10M+** total volume and live in the table for weeks.
* High-flow short-window markets — recurring "Up or Down" cycles on BTC / ETH / SOL that turn over volume every few minutes.
* Multi-outcome markets where each named outcome is shown as a separate sub-row in the Outcome column.

## Reading the row

* **Prognosis** — the question; multi-outcome markets show a `Show markets` action on the right to expand sub-outcomes.
* **Created / Ending** — how long the market has been live and when it resolves. Long-window markets dominate Trends because they have had time to accumulate volume.
* **Participants** — green / red split. A heavily skewed split (e.g. 75% / 25%) suggests strong directional consensus; even splits suggest a genuine coin-flip.
* **Volume** — the column Trends is sorted on. Watch the unit — thousands ("тыс."), millions ("M"), or billions ("B").
* **Outcome** — implied probability for the leading side, e.g. `Yes 71%`.
* **Quick Buy** — `Up / Down` at your defaults.

## When Trends is the right view

* You want fills at posted prices without slipping the market.
* You are scanning for direction signals — heavy volume shifts and skewed participant splits are more meaningful when liquidity is real.
* You want to verify a Pulse signal — switch to Trends and check the volume column.

{% hint style="info" %}
Trends shows the top-N by volume; obscure long-tail markets won't appear here even if they are open. Use [New](/graphdex-docs/research-predictions/new-markets.md) or [Bubble](/graphdex-docs/research-predictions/bubble.md) to see them.
{% endhint %}

## FAQs

<details>

<summary>Is the sort by 24h volume or all-time?</summary>

All-time volume on the market. Short-window markets (5-minute Up/Down cycles) reset frequently so their volume stays modest; long-window markets accumulate.

</details>

<details>

<summary>How do I trade a multi-outcome market like "FIFA World Cup Winner"?</summary>

Click the row to open the market page. Each outcome (Spain, France, Argentina, etc.) is its own line in the Outcomes panel with its own Up/Down buttons. See [Outcomes & Top Holders](/graphdex-docs/trading-predictions/outcomes-and-holders.md).

</details>

<details>

<summary>Why are some volumes shown as $ and others without?</summary>

Volumes are quoted in the platform's reporting unit, displayed with a \`$\` prefix and short-scale suffixes (K, M, B). A blank or \`$0\` row means no volume yet — usually a brand-new market that landed on Trends only because of category filtering.

</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/research-predictions/trends.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.