<p>Each node acts independently, the Bitcoin protocol is designed so that you do not have to trust any other nodes to verify the state of the network.  </p>

<p>If your node hears about a new block at the chain-tip, it will check to see if the block is valid according to the network's rules. Assuming the block is valid, it will be added to your local copy of the blockchain. </p>

<p>If your node later hears about a longer (valid) chain that doesn't include the block you just added, then you would 'reorganize' the last couple blocks, in order to create what you now know to be the longest chain. The previously accepted block would be discarded, and become what is commonly referred to as an 'orphan block'.</p>

<p>By this mechanism and the related game theory, the network's nodes are able to maintain consensus around the blockchain's history. The more confirmations a block has (ie blocks mined on top of it), the more certain one can be that it will not be 'reorganized', meaning the payment is more permanently included in the blockchain.</p>

CC BY-SA 4.0
2018-09-17T22:16:00.927Z
Thanks Chtrik, excellent answer. This clarifies any doubts I had on how an independent node can get information which is not residing in a central repository. Fascinating technology.
David Vella
CC BY-SA 4.0
2018-09-17T07:19:19.743Z
2018-09-17T07:19:19.743Z
chytrik
<p>Before posting a solved block to the longest chain, how many nodes would one need to check before making sure that the longest chain was found?</p>

<blockchain>
How many nodes would one typically check to determine the longest chain?
David Vella
# How many nodes would one typically check to determine the longest chain?

(Asked by: username_0 on 2018-09-17)

Before posting a solved block to the longest chain, how many nodes would one need to check before making sure that the longest chain was found?

**Tags:** blockchain


---

## 1 answers

### Answer by username_1 on 2018-09-17. Score: 0 | Accepted answer

Each node acts independently, the Bitcoin protocol is designed so that you do not have to trust any other nodes to verify the state of the network.

If your node hears about a new block at the chain-tip, it will check to see if the block is valid according to the network's rules. Assuming the block is valid, it will be added to your local copy of the blockchain.

If your node later hears about a longer (valid) chain that doesn't include the block you just added, then you would 'reorganize' the last couple blocks, in order to create what you now know to be the longest chain. The previously accepted block would be discarded, and become what is commonly referred to as an 'orphan block'.

By this mechanism and the related game theory, the network's nodes are able to maintain consensus around the blockchain's history. The more confirmations a block has (ie blocks mined on top of it), the more certain one can be that it will not be 'reorganized', meaning the payment is more permanently included in the blockchain.

> **Comments:**
> **username_0**: Thanks Chtrik, excellent answer. This clarifies any doubts I had on how an independent node can get information which is not residing in a central repository. Fascinating technology.  

---

