> 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 ## 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. * **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 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://userguide.cryptoquant.com/tr/cryptoquant-metrics/utxo/binary-cdd.md?ask=&goal= ``` `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.