You’re forked!

Getting resynced using the invalidateblock command and finding some new peers.

walkjivefly
May 1 · 3 min read
crown-cli getblockhash 2344133

Binary chop

Imagine the block chain laid out along a long horizontal line with the genesis block at the left end, and the current highest block at the right end.

  1. Compare your value of the blockhash for block 2342191 with what the explorer has.
  2. If they match move right (to block (2342191+2344133)/2 = 2343162), if they differ move left (to block (2340250+2342191)/2 = 2341220).
  3. Repeat steps 1–3 until you find the smallest block number with a mismatched hash. That’s the point at which you forked.
  4. Suppose the fork point is 2343087 and your hash for this block is 4b3bc3ae3b5e4870c11f23b116409dc29de4ac31a0a509c55a9d1b6841feb03

Invalidateblock

Use the debug console of the QT wallet, or the crown-cli command to invalidate the block. For example

crown-cli invalidateblock  4b3bc3ae3b5e4870c11f23b116409dc29de4ac31a0a509c55a9d1b6841feb031

Get some new peers

If you’re on a fork with a bunch of other nodes, none of them will be able to share the correct version of the block with you. You need some new peers.

  1. Remove the peers.dat file from the datadir.
  2. Restart your wallet.

Crown Platform

Crown is a digital token and blockchain platform enabling independence serving individuals & businesses. We are focused on legal compliance and transparency utilizing our decentralized governance model.

walkjivefly

Written by

Crown Platform

Crown is a digital token and blockchain platform enabling independence serving individuals & businesses. We are focused on legal compliance and transparency utilizing our decentralized governance model.