> For the complete documentation index, see [llms.txt](https://docs.candelacharts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.candelacharts.com/investing/macro-and-liquidity/bitcoin-dominance-trend/faqs.md).

# FAQs

Bitcoin Dominance Trend FAQs

<details>

<summary>What does BTC Dominance (BTC.D) represent?</summary>

BTC Dominance measures Bitcoin’s share of the total crypto market cap. A rising BTC.D usually means capital is flowing into Bitcoin, while a falling BTC.D suggests strength in altcoins.

</details>

<details>

<summary>How do the color shifts work?</summary>

If BTC.D is above the chosen moving average, the dominance line turns **bullish (green)**. If below, it turns **bearish (red)**.

</details>

<details>

<summary>Why are the levels 40%, 50%, and 65% important?</summary>

These levels represent historically significant thresholds where Bitcoin often shifts from dominance to weakness, influencing altcoin performance.

</details>

<details>

<summary>Can I change the symbol used for BTC.D?</summary>

Yes, the default is `CRYPTOCAP:BTC.D`, but you can modify it in the settings to test other dominance indices or assets.

</details>

<details>

<summary>How should I use this indicator in trading?</summary>

Use it as a **market context tool**. For example:

* If BTC.D is trending up → prefer Bitcoin over altcoins.
* If BTC.D is trending down → consider higher exposure to altcoins.

Always combine with price action, liquidity, and risk management.

</details>


---

# 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.candelacharts.com/investing/macro-and-liquidity/bitcoin-dominance-trend/faqs.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.