<p>I think the answer is the same as when you're receiving a Bitcoin transaction and you want to be "certain" that the coins are now actually yours and can't be double spent anymore: you wait for multiple confirmations (the whitepaper says 6).</p>

<p>In situations where you can't afford to wait (like mining) you'll just have to make a gamble and be ready to change your mind if reality forces you to do a re-organization. Meaning: discarding the last 1 or more blocks and replacing them with the new most-work tail.</p>

<p>So anything inquiring information from a full node, should also always be ready for a change of that information.</p>

CC BY-SA 3.0
2016-08-29T14:05:38.990Z
What I get out of the answer is that there's only a statistical confirmation but no sure way. Thank you for clarifying.
mprivat
CC BY-SA 3.0
2016-08-29T17:19:32.310Z
@mprivat Correct. If I remember correctly the Bitcoin whitepaper describes it as such. Under normal circumstances "6 confirmations" is considered pretty secure.
Jannes
CC BY-SA 3.0
2016-08-29T12:43:45.483Z
2016-08-29T12:43:45.483Z
Jannes
<p>Your node doesn't know for sure. Actually, nobody ever knows for sure that the current chain-tip will be in the chain with the most work, it just becomes increasingly likely as more time passes and additional blocks build on-top.</p>

<p>Once a sufficient number of blocks have been built on top of the observed block, it will be sufficiently unlikely that the observed block will end up in a stale chain-tip, and you can trust it. </p>

<p>Users make different judgment calls about the number of blocks they wait for: some don't wait for another block and accept at first confirmation, some wait three blocks, some require six. The extreme is likely to be the 100 block waiting period the network requires before mining rewards may be spent.</p>

<p>However, until proven wrong, the node will assume that he has the newest information: after all finding a block is an unlikely event, and thus will respond with information about his block when queried for the blockchain-tip.</p>

CC BY-SA 3.0
2016-08-29T14:10:58.443Z
2016-08-29T14:10:58.443Z
Murch
<p>I'm trying to understand how the mining process works. Specifically, my understanding is the local miner works on blocks and add them to their local blockchain if they succeed. It may turn out that this isn't the longest chain of blocks (because there are other miners working in parallel) and when that longest chain arrives at the miner, the miner will discard its local (shorter) subchain in favor of the new one.</p>

<p>My question is if the local node (who's also a miner) is asked for information from the block chain before that longest chain arrives, how would it know that these blocks may still change in the future and shouldn't necessarily be trusted?</p>

<p>I apologize if the whole question seems confused. It's only a reflection of my own confusion on the topic.</p>

CC BY-SA 3.0
2016-08-29T12:35:46.297Z
Note that the term "longest chain" is often used (even in the Satoshi whitepaper), but that method is actually flawed. "most-work chain" better describes what is in use these days. I don't think this alters your question though.
Jannes
<blockchain-fork><relay><chain-reorganization><best-chain>
How do I know I can trust the head of the blockchain
mprivat
# How do I know I can trust the head of the blockchain

(Asked by: username_0 on 2016-08-29)

I'm trying to understand how the mining process works. Specifically, my understanding is the local miner works on blocks and add them to their local blockchain if they succeed. It may turn out that this isn't the longest chain of blocks (because there are other miners working in parallel) and when that longest chain arrives at the miner, the miner will discard its local (shorter) subchain in favor of the new one.

My question is if the local node (who's also a miner) is asked for information from the block chain before that longest chain arrives, how would it know that these blocks may still change in the future and shouldn't necessarily be trusted?

I apologize if the whole question seems confused. It's only a reflection of my own confusion on the topic.

**Tags:** blockchain-fork, relay, chain-reorganization, best-chain

> **Comments:**
> **username_1**: Note that the term "longest chain" is often used (even in the Satoshi whitepaper), but that method is actually flawed. "most-work chain" better describes what is in use these days. I don't think this alters your question though.  

---

## 2 answers

### Answer by username_1 on 2016-08-29. Score: 1 | Accepted answer

I think the answer is the same as when you're receiving a Bitcoin transaction and you want to be "certain" that the coins are now actually yours and can't be double spent anymore: you wait for multiple confirmations (the whitepaper says 6).

In situations where you can't afford to wait (like mining) you'll just have to make a gamble and be ready to change your mind if reality forces you to do a re-organization. Meaning: discarding the last 1 or more blocks and replacing them with the new most-work tail.

So anything inquiring information from a full node, should also always be ready for a change of that information.

> **Comments:**
> **username_0**: What I get out of the answer is that there's only a statistical confirmation but no sure way. Thank you for clarifying.  
> **username_1**: @username_0 Correct. If I remember correctly the Bitcoin whitepaper describes it as such. Under normal circumstances "6 confirmations" is considered pretty secure.  

---

### Answer by username_2 on 2016-08-29. Score: 2

Your node doesn't know for sure. Actually, nobody ever knows for sure that the current chain-tip will be in the chain with the most work, it just becomes increasingly likely as more time passes and additional blocks build on-top.

Once a sufficient number of blocks have been built on top of the observed block, it will be sufficiently unlikely that the observed block will end up in a stale chain-tip, and you can trust it.

Users make different judgment calls about the number of blocks they wait for: some don't wait for another block and accept at first confirmation, some wait three blocks, some require six. The extreme is likely to be the 100 block waiting period the network requires before mining rewards may be spent.

However, until proven wrong, the node will assume that he has the newest information: after all finding a block is an unlikely event, and thus will respond with information about his block when queried for the blockchain-tip.


---

