> For the complete documentation index, see [llms.txt](https://gitbook-docs.coinmetrics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook-docs.coinmetrics.io/network-data/deprecated/watchtower-alerts-overview-deprecated/watchtower-alerts-deprecated/ethereum-proof-of-stake-alerts-deprecated/decrease-in-active-addresses-alert-deprecated.md).

# Decrease in Active Addresses Alert - DEPRECATED

<mark style="color:red;">**THIS ENDPOINT HAS BEEN DEPRECATED AND WILL NO LONGER BE ACTIVELY MAINTAINED, UPDATED OR SUPPORTED**</mark>

**Alert Definition**

Alerts if the Active Addresses of a given block are lower than its 100-block predecessors. Active Addresses represent the sum count of unique addresses that were active in the network (either as a destination or source of a ledger change) that block. All parties in a ledger change action (source and destination) are counted.

**Dictionary**

| Name                               | AlertID                                 | Category | Sub-category  | Type | Unit               | Interval |
| ---------------------------------- | --------------------------------------- | -------- | ------------- | ---- | ------------------ | -------- |
| Decrease in Active Addresses Alert | block\_active\_addresses\_rsd\_100b\_lo | Alert    | ETH PoS Alert | Sum  | Count of Addresses | Ad hoc   |

**Interpretation**

A consistent decrease in Active Addresses may be caused organically by seasonal decreases in demand, or may be a result of more concerning circumstances. If, for example, validators are censoring a group of addresses, blocks would not be fully empty, but Active Addresses would decrease.

**Potential Root Causes**

Natural drop in demand for block space, which tends to be seasonal. Potential censorship at the block producer level.

**Asset Coverage**

Ethereum (ETH)

\\


---

# 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://gitbook-docs.coinmetrics.io/network-data/deprecated/watchtower-alerts-overview-deprecated/watchtower-alerts-deprecated/ethereum-proof-of-stake-alerts-deprecated/decrease-in-active-addresses-alert-deprecated.md?ask=<question>&goal=<endgoal>
```

`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.