Quote from: YouIsPeng on April 11, 2014, 01:16:14 AM

Quote from: WALKEN-COIN on April 11, 2014, 01:10:36 AM

Quote from: YouIsPeng on April 11, 2014, 01:04:38 AM

WALLET SYNCING FIX

I have been having the same problem as many other people here where the wallet won't sync past block 8786. I have tried all of the fixes posted here and none worked. I did the following and my wallet is now working perfectly.

If you go to Help->Debug Window->Console in your wallet and type "getpeerinfo" you will get a list of all the nodes your wallet is connected to. This is where the wallet gets the blockchain info from. For each entry look at the "startingheight" number, this shows what block that particular node thinks we are on.

If you have lots of nodes that say: "startingheight" : 8786, or some other number in the 8000s then your wallet is going to get confused as it is getting conflicting information.

I simply went through and listed all the nodes that were showing the correct block number. (as of writing we are on 9658)

Now you want to stop your wallet from automatically searching for nodes to connect to, so it won't find and connect to these 'bad' nodes - this is done by using "connect=IP" instead of "addnode=IP".

So, to get your wallet working do exactly the following:

1) Shut down the wallet completely.
2) Go to C:\Users\YourUserName\AppData\Roaming\cleanwatercoin.
3) Delete everything EXCEPT wallet.dat and cleanwatercoin.conf.
4) Open cleanwatercoin.conf and delete everything then paste in the following and save.

connect=176.14.88.234
connect=107.170.217.4
connect=67.82.168.57
connect=97.102.24.119
connect=188.226.199.223
connect=water.suprnova.cc

5) Restart the wallet.

Your wallet will now download the blockchain ONLY from those 'good' nodes that are specified. This will take a little while, be patient but it should fully sync eventually.
Please post other 'good' nodes that you find so they can be added to the conf file in future.

Please let me know if this worked for you.

If the above works for you, AWESOME.

As far as I understand, you do not need a conf file unless you are using solo mining. I deleted my conf and used the method I posted above your post to synch it and it is working good.

So yeah, the conf file contained instructions to operate on bad nodes and seems to have messed with some stuff if you used it that way. The re-scan checkblock=0 seemed to fix that without a conf file in the folder.

Solo miners apparently need a conf file, so Peng's fix would be their bread and butter.

-Thanks peng for finding those bad nodes! I had asked about nodes in IRC but nobody was sure which ones could be the culprit. They did mention seeing the dreaded 8786 number in there though. Great job!

You're right, you don't need a .conf file but if you run it without one (or even with one that uses addnode=IP) your wallet will try to search for nodes on its own. The use of "connect=IP" in the .conf file ensures that it ONLY connects to nodes that you want it to, ie the nodes you know are on the right blockchain.

Excellent. I will delete my solution post for now, and see if this one works for everyone. If it does, we simply need to release a conf file or new wallet with correct file in it.

Yay!