> 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/market-valuation-and-on-chain/bitcoin-realized-price-bands/faqs.md).

# FAQs

Bitcoin Realized Price Bands FAQs

<details>

<summary><strong>What exactly is the "Realized Price"?</strong></summary>

The Realized Price is an on-chain metric. Instead of valuing each Bitcoin at the current spot price, it values each Bitcoin at the price it last moved on the blockchain. This effectively calculates the average cost basis of all holders.

</details>

<details>

<summary><strong>Can I use this indicator on Altcoins?</strong></summary>

No, this specific indicator fetches Bitcoin's specific on-chain Realized Cap data. It is only accurate for Bitcoin (BTCUSD, BTCUSDT).

</details>

<details>

<summary><strong>What does the MVRV Oscillator show?</strong></summary>

The MVRV (Market Value to Realized Value) ratio compares the current spot price to the Realized Price. A high MVRV indicates the market is holding large unrealized profits (bubble risk), while a low MVRV indicates aggregate unrealized losses (bottoming territory).

</details>

<details>

<summary><strong>How do I turn off the candle coloring if it conflicts with my chart?</strong></summary>

You can disable the custom candle coloring via the indicator's settings panel under the "Style" tab.

</details>

<details>

<summary><strong>How do I set up alerts for the signals?</strong></summary>

You can create standard TradingView alerts on the indicator and select the Long and Short crossover conditions to be notified when Bitcoin crosses critical macro valuation thresholds.

</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/market-valuation-and-on-chain/bitcoin-realized-price-bands/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.