Chain forks

Trouble syncing after hardfork with seemingly lost coins? Don't worry!

If you’re experiencing that Rhombus Core wallet is not syncing any further, then it might be because you got caught on a fork due to the latest hardfork.

If you execute any transaction during this time, it will appear as if you’ve lost the coins, but don’t worry. Nothing has left your wallet.

Getting your client back to a working state requires a bit of work.

Updating to the latest version will ensure that you have the latest list of “checkpoints”. These checkpoints are known blockhashes of the correct chain, which help guide the client guide itself to the right fork.

Sometimes the client will ban others nodes for misbehaving. It might be that your client has banned all legitimate nodes because you were on an older version. Open up the debug console and check whether you have any banned peers by listbanned. If that’s the case, consider clearing the list by executing clearbanned.

Sometimes the client will detect that it has made a mistake and will automatically get itself back on track.

Open up the debug console in Rhombus Desktop or Rhombus Core and execute the following command getchaintips. Look for any chains that are marked invalid. Get the corresponding hash of that chain and execute: reconsiderblock HASH_HERE, where HASH_HERE is value that was returned previously.

Take a look at the block explorer and verify that your client is syncing to the latest height indicated there. getblockchaininfo will return the height to which you’re synced. You might have to repeat step 4 again.