> 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/30-10-2026-smart-money-historical-holdings-balance-change.md).

# 30-10-2026: Smart Money Historical Holdings Balance Change Uses Token Amount

**Affected endpoint:** `smart-money/historical-holdings`

`balance_24h_percent_change` now measures the change in the token amount held by Smart Money since the previous day. It previously measured the change in USD value, so a token price move showed up as a balance change even when holdings were flat. For example, ZEC on Solana for 2026-10-15 changes from `-0.0899` to `-0.0015`.

The value remains a fraction (`0.1` = +10%). Other changes:

* The first requested date is compared with the previous day. It previously always returned `0`.
* A token that Smart Money did not hold the day before returns `1`. It previously returned `0`.
* A token that returns after a day with no Smart Money holding returns `1`. It previously compared with the last day it was held.
* A previous-day holding under 0.0001 tokens counts as no holding, so the value is `1`. A tiny leftover amount previously produced changes in the hundreds of millions.

`value_usd`, `balance`, `holders_count`, `share_of_holdings_percent`, filters, sorting and pagination are unchanged. The `balance_24h_percent_change` filter and sort now apply to the new values.

**Rollout:** Settled historical requests can remain cached for up to 7 days, so identical requests may return the previous values until those entries expire. Ranges that include today or end within the last 2 days use a 5-minute cache.


---

# 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/30-10-2026-smart-money-historical-holdings-balance-change.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.
