# PlanB 200WMA Indicator

##

## 200-Week Moving Average (200WMA) Indicator

### Summary

The **200-Week Moving Average (200WMA)** is a long-term Bitcoin valuation benchmark.

* It smooths out price action by averaging the last 200 weeks.
* Serves as a **“floor” indicator** during bear markets.
* Highlights long-term trend growth independent of short-term volatility.

***

## Steps to Use the 200WMA Indicator

**1.  Understand the concept**

* Moving average: Arithmetic and geometric versions are used.
* Time horizon: 200 weeks ≈ 4 years (one halving cycle).
* Purpose: Identify Bitcoin’s long-term trajectory.

&#x20;**2.  Interpret the 200WMA Chart**

* Black line: 200-week arithmetic mean.
* Gray line: 200-week geometric mean.
* Colored dots (BTC Price): Represent months until halving

**3.  Analyze Historical Patterns**

* Bear market lows: Price often touches or slightly dips below 200WMA
* Bull markets: Price remains far above the moving average.
* Trend growth: 200WMA steadily rises, reflecting adoption and scarcity.

4\.  **Make Decisions**

* At or near 200WMA: Historically strong long-term accumulation zones.
* Above WMA: Reflects confidence, but watch for overheating.
* Compare arithmetic vs. geometric: Provides different valuation lenses.

&#x20;Tips

* Use 200WMA as a **macro floor model**.
* Track deviations to identify overvaluation or undervaluation.
* Combine with RSI to align timing with momentum.
* Monitor halving dots to anticipate supply-driven cycles.
* Prefer log scale charts to view exponential growth clearly.

***

***

## Created By

### Created By: This indicator is a widely recognized tool in Bitcoin technical analysis.


---

# Agent Instructions: 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:

```
GET https://docs.blockhorizon.io/chart-tutorials/planb/planb-200wma-indicator.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
