# Network forking?

So with the ongoing dust storm I’ve been looking at peer statistics, to see how far behind my peers are. Just now I got this output:

``````\$ chia show -c|grep Height|sort -r -n -k3|uniq -c
8                                  -SB Height:  1078309    -Hash: d17b80d7...
11                                  -SB Height:  1078308    -Hash: f0696f57...
5                                  -SB Height:  1078308    -Hash: a372d0e1...
30                                  -SB Height:  1078307    -Hash: accd82dd...
1                                  -SB Height:  1078303    -Hash: 455b0131...
2                                  -SB Height:  1078299    -Hash: dc014bf8...
2                                  -SB Height:  1078290    -Hash: 320ed3c7...
1                                  -SB Height:  1078281    -Hash: d922f6f5...
``````

This shows how many peers are at which height, sorted by height.

The worrying part is that there are two entries for block 1078308, with different block hashes. So these peers don’t agree on what is the correct block 1078308. In my understanding this means the network is forking. People on the wrong fork will farm in vain, right?

Is this expected during a dust storm? Is there something to protect my own farmer, i.e. make it more likely to be on the “right” fork? Like in this case, kicking the 5 minority peers that have a different block 1078308 from the majority 11.

3 Likes

Wow i hope that is only a symptom of the dust storm… did you find any more info on this?

Acording to https://www.chiaexplorer.com/

The correct hash is: 0xa372d0e1e2b698b158d7a3355312f75c4d4ee2cebce387767c50c0668b4c7db9

https://www.chiaexplorer.com/blockchain/block/0xa372d0e1e2b698b158d7a3355312f75c4d4ee2cebce387767c50c0668b4c7db9

I could be wrong, but I thought block re orgs happened after issues like this occurred, resulting in a fix and return to normality.

It would be interesting to inspect the code; then collect measurements if the behavior is out of specification.