# Persistent Mining Pool Conflict 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 miners disagree on which version of the blockchain to build upon over the course of three blocks.

**Dictionary**

| Name                                  | AlertID                                    | Category | Sub-category  | Type | Unit   | Interval |
| ------------------------------------- | ------------------------------------------ | -------- | ------------- | ---- | ------ | -------- |
| Persistent Mining Pool Conflict Alert | persistent\_mining\_pool\_conflict\_3b\_hi | Alert    | Mining Alerts | Sum  | Blocks | Ad hoc   |

**Interpretation**

The blockchain fundamentally serves as a coordination mechanism for its users. When miners put together a new block of transactions, they often choose the most recently-mined block to build upon. Once a miner is successful, all other miners are expected to stop their work and create yet another block template that builds upon that miner's block. While that is the expectation, there are conditions that may lead mining pools to disagree on which block to build upon. Such disagreements can lead to network disruptions such as blockchain reorganization events, or reorgs.

**Potential Root Causes**

A mining pool might not be seeing the same block(s) as others due to connectivity problems at the P2P layer.

The network might have experienced a stale block and/or reorgs.

A 51% attack might have been launched and mining pools are uncertain as to which branch of the blockchain to build upon.

Potential bugs with mining pool firmware and/or supporting software.

**Asset Coverage**

Bitcoin (BTC)

\
\\


---

# 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://gitbook-docs.coinmetrics.io/network-data/deprecated/watchtower-alerts-overview-deprecated/watchtower-alerts-deprecated/mining-alerts-deprecated/persistent-mining-pool-conflict-alert-deprecated.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.