> For the complete documentation index, see [llms.txt](https://docs.nansen.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nansen.ai/api/changelog/14-10-2026-dated-smart-trader-labels-deprecation.md).

# 14-10-2026: Smart Trader Covers All Windows; Dated Smart Trader Labels Deprecated

On October 14, 2026, the `Smart Trader` label started covering every Smart Trader window. A wallet that qualifies as a `30D Smart Trader`, `90D Smart Trader` or `180D Smart Trader` now also carries `Smart Trader`. Filters on `Smart Trader` therefore return more wallets than before: roughly twice as many, because the label previously covered only all-time Smart Traders. Label lists in responses include `Smart Trader` next to the dated labels. Historical data before October 15, 2026 is not backfilled; history filters on `Smart Trader` also match the dated labels on earlier dates.

The dated values `30D Smart Trader`, `90D Smart Trader` and `180D Smart Trader` are therefore deprecated in Smart Money label filters. They are still accepted temporarily and return the same wallets as before. Use `Smart Trader` instead. We may begin rejecting the dated values after January 15, 2027.


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nansen.ai/api/changelog/14-10-2026-dated-smart-trader-labels-deprecation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
