Crown Forum

Author Topic: Update regarding master/systemnode statuses  (Read 3705 times)

higherbridge

  • Administrator
  • Sr. Member
  • *****
  • Posts: 62
  • Karma: +4/-0
  • Community Ambassador
    • View Profile
Update regarding master/systemnode statuses
« on: December 26, 2017, 07:20:09 pm »
Note: this is a copy of this post on our BCT ANN and will not reflect any edits made to the original post. See the original for the most up-to-date version.

Crown Network Status update:
Today at approx 11 AM CET 200 nodes where brought online within a short period of time. At the same time, a large miner experienced technical issues with their wallet, which points to the problematic governance system, which we are currently working on to fix..
These two isolated incidences caused a ripple throughout the network, which caused the masternode and systemnode lists to become fragmented, which is also why you would see some nodes offline one minute, and online the next minute.

Recommended course of action:
Don't restart your nodes, node-vps.com still shows 1062 masternodes online, so we do have a complete nodelist on the network, it just needs to be propagated throughout the network again.

One way of solving this is to use the following old nodes to connect to, to quicker get a new nodelist for both types of nodes.
Current blockheight as of this writing is: 1685692


Do the following to sync to correct nodes:
Add the following lines to crown.conf:
addnode=149.56.109.178:9340
addnode=54.36.78.142:41346
addnode=54.37.241.206:35544
addnode=80.209.232.6:34912

Or open the debug console(Tools->Debug Console) and type the following:
addnode 149.56.109.178:9340 add
addnode 54.36.78.142:41346 add
addnode 54.37.241.206:35544 add
addnode 80.209.232.6:34912 add


This also means that we are defining node-vps' version of the node list as the truth, so some nodes will become missing/expired, but it should keep most online - and stabilize the network over the next 24 hours
Some nodes might be stuck on an earlier block - you will need to delete mncache.dat, mnpayments.dat, peers.dat, sncache.dat, snpayments.dat, budget.dat, then restart the wallet with -reindex. - See this post for detailed explanation: https://forum.crown.tech/index.php?topic=83
« Last Edit: December 26, 2017, 10:46:51 pm by EdwardMorra »