So are people having issues with forked chain still? Yesterday's incident was due to a minor code bug.
But it has been rectified and chain is stable again. I've written a quick guide below on how to check.How to check that you are on the correct chain
1. Go to this MN info page and note the block number & its hash:http://18.104.22.168/~pub/DN/DN_masternode_payments_stats.html
2. Now go to your wallet and from the CLI / console, run "./darknet-cli getinfo" or "getinfo"
3. Ensure that your block number is at or just few blocks ahead of the one on the MN info page.
- If your wallet is behind that block, try restarting the wallet via "./darknet-cli stop" then "./darknetd" (if Windows, just close/relaunch)
- Then wait few minutes, then check tge getinfo output again. If the block doesn't move and it's behind still, then go to step 5.
4. If your wallet shows same block or just few infront, try running "./darknet-cli getblockhash xxxxxx" or "getblockhash xxxxxx".
- Replace xxxxxx with the block number shown on the MN info page. This will return a hash output.
- Make sure this hash matches the hash shown on the MN info page for that same block. If it does, you are on the right chain!
- But if you don't have 2 addnode IPs (below) & bantime=50 in your conf file, it is recommended to add them & restart it still.
5. If the hash for the same block does NOT match, then you are on the wrong chain. You will need to resync the blockchain.
- You need to stop the wallet, then delete the blocks & chainstate folders in your blockchain folder.
- Make sure your darknet.conf file has only the following 2 addnodes IP addresses.
- Also add the line bantime=50 to the bottom.
6. Then either replace them with a known good backup copy you made then restart the wallet or just restart the wallet to resync from scratch.
- To backup a good copy of the blockchain, you just need to copy the 2 folders (blocks & chainstate) while the wallet is not running.
7. Wait till it is resynced then repeat the above steps to check.