Crown Forum

Author Topic: UNINTENTIONAL CHAIN SPLIT - PLEASE READ CAREFULLY  (Read 59 times)

higherbridge

  • Administrator
  • Sr. Member
  • *****
  • Posts: 50
  • Karma: +4/-0
  • Community Ambassador
    • View Profile
UNINTENTIONAL CHAIN SPLIT - PLEASE READ CAREFULLY
« on: June 12, 2018, 10:35:02 pm »
UNINTENTIONAL CHAIN SPLIT RESOLVE

After intensively monitoring the situation around the fragmentation of the chain, the development team would like to give you an update on the current situation.

To make sure your wallet, Masternode, Systemnode or mining rig are on the correct chain, please perform the following steps.

PLEASE NOTE: THIS IS A PREPARATORY MEASURE. Exchanges and Crown services may not be on the correct chain yet! Before you send any CRW tokens, make sure both you and the receiver are on the correct chain! We are working closely together with exchanges and miners and hope to have all parties on the correct chain soon.


CHECK
Wallet > Tools > Debug Console:
Code: [Select]
getblockhash 1912453
On a VPS:
Code: [Select]
crown-cli getblockhash 1912453
EXPECTED RESULT
The above command should output
Code: [Select]
6e462923cff2e473b828b0306f8c0b915a54f154f0ea367903daa78a9e0ed551
FIX
Should the blockhash you see not be what was expected above, enter the following command:

Wallet > Tools > Debug Console:
Code: [Select]
reconsiderblock ae5d085e61b5b49e8de3efe3d22757685d350783fe971aeeac507d8d6d8d2296
On a vps:
Code: [Select]
crown-cli reconsiderblock ae5d085e61b5b49e8de3efe3d22757685d350783fe971aeeac507d8d6d8d2296
NEXT STEPS
Re-run the 'getblockhash' command and check its output. If it outputs the expected hash, you are on the correct chain and no further action is necessary. Let your node sync until it matches up with the block height on https://chainz.cryptoid.info/crw/.
However, you may need to restart your Masternodes or Systemnodes from your local wallet, but please open your VPS terminal and enter 'crown-cli [masternode/systemnode] status' This command outputs the definitive status of your incentivized node.

TROUBLESHOOTING
Should the above steps not work for you, please check if you entered all commands correctly.
You may have to wait a few minutes for the 'reconsiderblock' command to take effect. If after executing this command the blockhash is still incorrect, reindex your client.

Wallet > Tools > Wallet Repair > reindex

On a VPS, execute the following command:
Code: [Select]
crown-cli stop && sleep 5 && crownd -reindex

Should it happen that you’re still stuck, you can contact our support team through email (support@crown.tech) or in our Tech Support channel on Mattermost (https://mm.crownlab.eu/crown/channels/tech-support).



Thank you for your patience,

The Crown development team