> 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/mvrv-ratio/faqs.md).

# FAQs

MVRV Ratio FAQs

<details>

<summary>What exactly is MVRV?</summary>

It’s the ratio of the network’s market cap to its realized cap (sum of coins priced at last on-chain move). Values above 1 mean market value exceeds holder cost basis; far above 1 often marks frothy phases.

</details>

<details>

<summary>Why those fixed levels (3.5 / 2.5 / 1.0 / 0.8)?</summary>

They’re widely watched cycle landmarks: 1.0 ≈ fair value, 0.8 ≈ stress, 2.5–3.5 ≈ elevated to extreme euphoria. Use them as guides, not guarantees.

</details>

<details>

<summary>Do σ bands repaint?</summary>

No. The bands use historical mean/stdev over a fixed lookback and update only as new bars arrive; completed bars don’t change after close.

</details>

<details>

<summary>Does the script compute MVRV itself?</summary>

No. It reads curated MVRV series for BTC/ETH and plots them with added logic (levels, zones, bands). That keeps the output consistent with trusted data sources.

</details>

<details>

<summary>Why use “lookahead on” in the code?</summary>

To align historical MVRV values precisely with past bars when requesting the series, avoiding off-by-one shifts—visual accuracy matters for threshold touches.

</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/mvrv-ratio/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.
