> For the complete documentation index, see [llms.txt](https://docs.fyuz.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fyuz.fun/changelog/2026/july-2026-trader-tools-and-live-streaming.md).

# 📊 July 2026 — Trader tools & live streaming

## The terminal update

Six tool sections that turn Fyuz from a launchpad into a full trading terminal:

* **Discover** — Trending / New / Gainers / About-to-Graduate tabs with market-cap, volume, holder, age and status filters.
* **Portfolio** — cost basis, realized + unrealized PnL and ROI for every position, computed from your on-chain history.
* **Wallet explorer** — any address's full track record: trades, PnL, win rate, volume.
* **Token analytics** — holder concentration, creator holdings, buy/sell pressure, bundle detection and graduation progress on every token page.
* **Top Traders** — per-token PnL leaderboards with creator/whale labels.
* **Live streaming** 🔴 — creators broadcast camera, mic or screen natively on their token page, with live viewer counts and in-page chat.


---

# 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://docs.fyuz.fun/changelog/2026/july-2026-trader-tools-and-live-streaming.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.