> For the complete documentation index, see [llms.txt](https://userguide.cryptoquant.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://userguide.cryptoquant.com/tr/cryptoquant-metrics/utxo/binary-cdd.md).

# Binary CDD

Binary CDD is binary value and if Supply Adjusted Coin Days Destroyed (Supply-Adjusted CDD) is larger than average Supply-Adjusted CDD, Binary Coin Days points to '1' and points to '0'

## Definition

Binary Coin Days Destroyed is binary value and if Supply Adjusted Coin Days Destroyed is larger than average Supply Adjusted Coin Days Destroyed, Binary Coin Days points to ‘1’ and points to ‘0’ if not

* **shows 1:** If measured Supply-Adjusted CDD is larger than the average Supply Adjusted CDD
* **shows 0:** If measured Supply-Adjusted CDD is less than the average Supply Adjusted CDD

## Interpretation

It shows whether long-term holders’ movements are higher or lower than average.&#x20;

* **High density** of value pointing ‘1’: Long-term holders moved their coins for possible selling
* **Low density** of value pointing '1' : Long-term holders are not moving their coins


---

# 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://userguide.cryptoquant.com/tr/cryptoquant-metrics/utxo/binary-cdd.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.
