# Dealing with conflicts

This video is an additional video that you can watch if you wish to understand how the network resolves the issue of conflicting blocks. It happens every now and again that two valid blocks are produced at close to exactly the same time and that some nodes on the network receive them in a different order than other nodes. Then what? This video is rather technical but dives into how the protocol of the Bitcoin network resolves this issue.

| Creator              | Time  | URL                                                        |
| -------------------- | ----- | ---------------------------------------------------------- |
| Andreas Antonopoulos | 11min | [Full source](https://www.youtube.com/watch?v=fw3WkySh_Ho) |

{% embed url="<https://www.youtube.com/embed/fw3WkySh_Ho?end=2754&start=2058>" %}

{% hint style="info" %}
**Takeaway** The longest chain of valid blocks (the one with the most proof of work) is considered the true one. If two valid blocks are propagated across the network at the same time and there is temporary disagreement among nodes, the disagreement automatically gets resolved by miners voting with their computing power on which chain to work. Because this disagreement happens every now and again at the very edge of the blockchain (last blocks), Bitcoin transactions are considered fully confirmed after 6 blocks, although fewer confirmations are generally okay.
{% endhint %}


---

# 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://btcjourney.gitbook.io/start/how-does-bitcoin-work/what-is-happening/dealing-with-conflicts.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.