[Donated $2k+ To Charity] Clean Water Coin: A Crypto Charity (Pure PoS)

[endchat]

Bittrex wallet is disabled as well

This sucks

[ghostbackwards]

Bittrex wallet is disabled as well

This sucks

Yeah it is down.

[IntroVert]

Bittrex wallet is disabled as well

This sucks

Yeah it is down.

That's odd because market history shows trade after you posted that screenshot (see c/p from Bittrex below). Could it be issue with their platform instead of the CWC wallet?

Date                                    Bid/Ask            Total Units (WATER)    Total Cost (BTC)
04/10/2014 12:37:46 PM    0.00000017    25000.00000000    0.00425000
04/10/2014 12:25:04 PM    0.00000017    514.52779000            0.00008746
04/10/2014 12:17:31 PM    0.00000017    32.44797300            0.00000551

[ghostbackwards]

Bittrex wallet is disabled as well

This sucks

Yeah it is down.

That's odd because market history shows trade after you posted that screenshot (see c/p from Bittrex below). Could it be issue with their platform instead of the CWC wallet?

Date                                    Bid/Ask            Total Units (WATER)    Total Cost (BTC)
04/10/2014 12:37:46 PM    0.00000017    25000.00000000    0.00425000
04/10/2014 12:25:04 PM    0.00000017    514.52779000            0.00008746
04/10/2014 12:17:31 PM    0.00000017    32.44797300            0.00000551

It should just be deposits and withdrawals that are disabled. The market of existing coins on bittrex can still occur.

[NcHawkeye]

Make sure you delete all files associated with the wallet (except wallet.dat and conf) before you download the new wallet and it should work. If it gets stuck try restarting the wallet a few times.

[zero3112]

Whats up with the hard fork coming?

[NcHawkeye]

Whats up with the hard fork coming?

The hardfork has already happened. The OP just needs to update the title and first post lol

[endchat]

Make sure you delete all files associated with the wallet (except wallet.dat and conf) before you download the new wallet and it should work. If it gets stuck try restarting the wallet a few times.

Done and done, sevreal times...still stuck

[WALKEN-COIN]

I am stuck as well, after it worked last night. Not sure what is going on, but when it was synching last time I wiped and re-installed, I saw that it was telling me that "xxxx of 8687" was downloaded. When it reached the 7000 block, the message changed to it was downloading "xxxx of 8786.  So basically it reversed the 687 and made it a 786.

So is there some weird loop at the 8687/8786? Are they mixed up with each other?

[voxelot]

This fix will work.  Or if you keep reading a few posts down you will see a fix that uses correct nodes.

Given all the distress trying to synch the blockchain, I've created a blockchain bootstrap.

https://mega.co.nz/#!BZV3FSSA!iioQTDpzhDi1AbpgnImzULrV5clCdVACMa1MKIylUwo

Contains:
blk0001.dat
blkindex.dat
Up to block 9593

Download and extract to your %appdata% folder.

Donations Appreciated: CWC 5Z4DuRaLSs7Fa7FWdoLf9hH2dCkm4z9yHi

Thanks to everyone for working on this.

[WALKEN-COIN]

I'm getting in my VM now to try and find more work arounds.  I have to try and break things first since my wallets keep syncing.  The only thing that I notice slightly similar to these hang ups is blocks jumping back and forth while syncing.  Could be the network, just keep trying for now.

*EDIT*

I managed to replicate the error and was able to eventually sync the wallet after getting stuck on block 8786.  The only thing I can say is to just keep trying it.  Be careful while you do this but:

First backup your wallet.dat to an external drive or place it in a folder you wont be touching.

Do not use a .conf file while getting this wallet to sync.

Delete everything from %appdata%\Roaming\cleanwatercoin accept for wallet.dat.  Try reloading the Qt client.. it probably won't sync past 8786... try it again.. it probably wont sync... try moving you wallet.dat file and deleting the whole cleanwatercoin folder... relaunch client and close it down... replace new wallet.dat with old wallet.dat... see if it syncs.. it probably won't.. try again.. it will eventually sync.

I know it's frustrating to have to do this but it just seems like the wallet needs a chance to find the right network but it will eventually.

Yes and thanks for all your help in IRC Vox, you have been awesome.

Just want to add, these are workarounds, not fixes. The fixes are coming, but coders are coding when off work and have time at night.

[I_M]

Given all the distress trying to synch the blockchain, I've created a blockchain bootstrap.

https://mega.co.nz/#!BZV3FSSA!iioQTDpzhDi1AbpgnImzULrV5clCdVACMa1MKIylUwo

Contains:
blk0001.dat
blkindex.dat
Up to block 9593

Download and extract to your %appdata% folder.

Donations Appreciated: CWC 5Z4DuRaLSs7Fa7FWdoLf9hH2dCkm4z9yHi

[crypto_ripper]

Mine also gets stuck on 8786.

[YouIsPeng]

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
connect=95.85.45.65
connect=107.170.209.91
connect=173.209.34.2
connect=68.168.113.90

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.

*edit* node list updated 13/4/14

[WALKEN-COIN]

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!

[YouIsPeng]

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.

[WALKEN-COIN]

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!

[WALKEN-COIN]

Peng, your solution worked flawlessly. My wallet immediately showed it was synching to the 9000 blocks when I started it up.

GREAT work. That will make a lot of people happy.

A lot of people have worked a lot on this set of issues in the last few days, pretty much non-stop. It was a pleasure watching everyone work together.


edit: and it is synching FAST!

[endchat]

Peng's fix works flawlessly.

One question, the conf file is supposed to be in the roaming/cleanwatercoin folder or is it supposed to be in the wallet qt folder?

[voxelot]

Peng's fix works flawlessly.

One question, the conf file is supposed to be in the roaming/cleanwatercoin folder or is it supposed to be in the wallet qt folder?

Awesome job Peng, glad to see you found a way to exclude the nodes with bad block heights on my new wallet!

.conf will go in the roaming folder.