Copied over from the official Discord:
In an attempt to help stabalize the Vitality blockchain and bring the community together, I am launching a campaign to increase community awareness of the issues, decrease all the FUD going on lately, and help people with common problems. My posts have 4 goals:
1. Help users solve the recently common “missing transaction/syncing issues” in the wallet.
2. Help Masternode Holders check if their masternode is on the right chain.
3. Get all MNs and Wallets on the right chain so we don’t have any more problematic forks.
4. Alleviate community fears about the project by stabilizing the network so the Devs can smoothly roll out new updates and continue working on improving Vitality instead of using their time to help fix our issues.
MISSING WALLET TRANSACTION/SYNCING ISSUES
If you need to fix a problem with a missing transaction or your wallet not syncing, follow these easy steps:
1. Make sure your wallet is closed, then make a backup copy of your wallet.dat file somewhere safe. (Found in [User]/Appdata/Roaming/Vitality)
2. Delete everything in that folder EXCEPT for your Vitality.conf file and wallet.dat file.
3. Open the Vitality.conf file in notepad, delete anything in there, and copy and paste the following working nodes in (these are checked daily to make sure that they are on the right chain), then save and close notepad:
addnode=178.216.200.181:15415
addnode=199.247.19.92:15415
addnode=149.28.45.124:15415
addnode=149.28.38.204:15415
addnode=149.28.98.142:15415
addnode=144.202.43.164:15415
4. Relaunch Vitality-qt.exe and wait for it to resync. Everything should be working now.
MN HOLDERS – CHECKING THE CHAIN YOUR MASTERNODE IS RUNNING ON AND CORRECTING IT IF NECESSARY (Thanks goes to @JakubGGG#8255 for writing the basis for this guide)
To all MN Holders: Please check your Masternodes to make sure they are not forked. It is apparent by looking on the peer list that some of them are at the wrong height. People are having problems with syncing their wallets because they are connecting to these nodes and downloading the wrong chains. As Masternode Holders who want Vitality to succeed, we must step up and help fix the problem to better stabilize the blockchain.
To check that your Masternode is on the right chain, follow these easy steps:
1. Login to your VPS (Using PuTTY, etc.)
2. Type the following command to check your block height:
./Vitality-cli getmininginfo
(Check if it's the correct block height with the explorer:
http://104.236.203.128/)
3. If the Masternode is not on the correct height, then do the following on your VPS:
Reboot your VPS (wait a minute or two and login again through PuTTY)
Type the following to delete the wrong chain and resync to the proper one:
cd .Vitality
rm -r blocks
rm -r chainstate
4. Run the daemon again and wait for it to fully sync (wait 1-3 min to be safe):
./Vitalityd -daemon
5. Check the block height again to make sure it matches the explorer (
http://104.236.203.128/):
./Vitality-cli getmininginfo
Congrats! Hopefully that did it for you! If that did not fix your issue, please post in the #help channel and someone will try and help you resolve the issue. If everyone does this, the chain will stabilize and we should no longer have forking issues.
Answers to likely questions:
1. No, I’m not affiliated with the project in an official capacity and I do not have a direct line to the developers. I’m just a fan of the project that wants it to succeed and has extra time on their hands.
2. There is no confirmation that the developers are gone! @Rajesh-Vitality#8124 was on discord as recently as 5/9/17 helping someone with Masternode issues.
3. The developers don’t have time to deal with our problems for half of the day if you want them to make improvements to the project. On 5/5/17 they announced they are working on a tiered Masternode system, so my guess is that is what they are doing instead of chatting with us on discord. So that is why some members of the community are going to start stepping up. No MN were presold and running off with the amount that was premined would get them very little money for the amount of work that was put in, so I don’t believe they are gone at this point. There is no need for all the FUD, it’s all random gossip and fearmongering at this point.
4. I will be posting the above information twice a day on discord, Saturday and Sunday, and once a day for the following five days. Spreading awareness and getting everyone on the same chain, and page regarding the state of the project, is VITAL to its success. This is a good concept and will happen regardless if Vitality achieves success or another coin down the road. Let’s help Vitality succeed and have things ready for the Devs to implement tiered masternodes and other future updates into the project.
@everyone
