One of the many things that could go wrong in a decentralized environment such as blockchain, is keeping things in sync. This is why the consensus protocol is such a critical component of the technology. How do you know for sure that your copy of the blockchain has forked from the mainstream? Here's a script that could help.
For a general review of the posts involving WORX coin, you may want to visit any of the posts below:
* WORX Wallet "bootstrap.dat" File (Alternate Method)
* Create a WORX Wallet "bootstrap.dat" File
* Worx-Calculator Spreadsheet Shared
* Conclusion: WORX Staking vs MasterNode Study
* PoS: Setup Staking Wallet with Worx Coin
* Data-Driven Decision: Stake Coins vs Masternode Collateral
You may download the node-debugger.sh script from my github repository.
This is how it looks when the Explorer blockchain don't match that of the wallet's local copy. (Just so I could give an example, I ran a copy of the previous version of the wallet. It is expected to fork and will not be in sync with the WORX blockchain.)
While on an in sync wallet, you will find a similar view as below.
Again, this is a little biased towards Linux VPS instances as the majority of the masternodes are Linux-based.
To execute, download the script and run it:
[worx@vhost ~]$ wget https://raw.githubusercontent.com/dillagr/worx-calculator/master/node-debugger.sh
[worx@vhost ~]$ bash node-debugger.sh
If this script has helped you in any way, send me a tip via this WORX address: WShjWUBHmXaiuqauauhMeDK93S3ac2xDXC
Time for a couple of gratuitous shots of one of my b...
@c0ff33a
@enginewitty