Topic: [Donated $2k+ To Charity] Clean Water Coin: A Crypto Charity (Pure PoS) - page 57. (Read 195717 times)
May 03, 2014, 12:55:50 PM
I received a tx from the auto payout - so thats working... but I'm still waiting on a manual cash out from before... this is my second manual ... received the first.
May 03, 2014, 12:30:57 PM
We just fired back up the AP cron on the official pool. If anyone is on there can you help confirm/deny this? Thanks!!
May 03, 2014, 12:25:53 PM
DEV he hires only do patch job and get paid not thing else he cares. So he could get hire again to patch the wallet or compile Mac version of Wallet Huh Smiley
Sum up, the coin wallet still have bug. Please change wallet version number when make any improvement. always cleanwatercoin version 1.6.0.0 make people confusing and unprofessional. Especially those who get paid and don't have time to change it. Change the cleanwatercoin-qt.exe file name to cleanwatercoin-qt_4.exe Roll Eyes everyone can do it.
Smiley Good news hash rate is up and price, too.
Miner beware of fork when solo or pool mining may come in later again. Even official pool Huh Please check blockchains when in doubt. Thanks
The blockchain is now 27811
I got the same issue. I'm tired of resync wallet. I wasted a lot of time for this. Thanks
Sum up, the coin wallet still have bug. Please change wallet version number when make any improvement. always cleanwatercoin version 1.6.0.0 make people confusing and unprofessional. Especially those who get paid and don't have time to change it. Change the cleanwatercoin-qt.exe file name to cleanwatercoin-qt_4.exe Roll Eyes everyone can do it.
Smiley Good news hash rate is up and price, too.
Miner beware of fork when solo or pool mining may come in later again. Even official pool Huh Please check blockchains when in doubt. Thanks
The blockchain is now 27811
I got the same issue. I'm tired of resync wallet. I wasted a lot of time for this. Thanks
May 03, 2014, 11:58:00 AM
RejectMining has found this error again!
"errors" : "WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers."
Lovely, working on re-sycning to get it back online now.....
I woke up to the invalid checkpoint error again too.
I deleted the conf altogether and have no conf now.
I seem to be on the latest block 27675, But I also have that message on the wallet now.
very weird...and Lovely indeed...
May 03, 2014, 11:34:12 AM
attempt #3:
"errors" : "WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers."
I have no addnodes actually, since the default ones worked about a week ago. I thought these problems were over
"errors" : "WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers."
I have no addnodes actually, since the default ones worked about a week ago. I thought these problems were over
Wild, 3 attempts..I resync'd pretty quick on 1st try (didn't hurt that I had backup from block ~22K) ..new back up made and wallet seems to be ticking away.
The pool seems to work again if client restarts, which is odd to see stratum issue anyway.
Now that I've tackled that, I'm gonna go spend 1BTC on voting..
I could use 1BTC of dr. pepper while I wait for this to re-re-re-re-re-re-re-re-re-re-re-re-re-re-re-re-re-re-re-re-re-re-sync...
May 03, 2014, 11:32:39 AM
attempt #3:
"errors" : "WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers."
I have no addnodes actually, since the default ones worked about a week ago. I thought these problems were over
"errors" : "WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers."
I have no addnodes actually, since the default ones worked about a week ago. I thought these problems were over
Wild, 3 attempts..I resync'd pretty quick on 1st try (didn't hurt that I had backup from block ~22K) ..new back up made and wallet seems to be ticking away.
The pool seems to work again if client restarts, which is odd to see stratum issue anyway.
Now that I've tackled that, I'm gonna go spend 1BTC on voting..
May 03, 2014, 11:28:09 AM
When it rains it POURS! Now the main pool is dead, throwing a stratum JSON auth error.
My wallet died with the invalid checkpoint issue..
And somewhere a frog got run over by a car.
So!
My wallet died with the invalid checkpoint issue..
And somewhere a frog got run over by a car.
So!
Well then it only makes sense that we all vote for cwc on MintPal because surely it is ready. *sarcasm*
This is why I didn't vote for it yet; I wanted to see at least a week of stable wallets....
May 03, 2014, 11:27:32 AM
attempt #3:
"errors" : "WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers."
I have no addnodes actually, since the default ones worked about a week ago. I thought these problems were over
"errors" : "WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers."
I have no addnodes actually, since the default ones worked about a week ago. I thought these problems were over
May 03, 2014, 11:27:09 AM
When it rains it POURS! Now the main pool is dead, throwing a stratum JSON auth error.
My wallet died with the invalid checkpoint issue..
And somewhere a frog got run over by a car.
So!
My wallet died with the invalid checkpoint issue..
And somewhere a frog got run over by a car.
So!
Well then it only makes sense that we all vote for cwc on MintPal because surely it is ready. *sarcasm*
May 03, 2014, 11:21:01 AM
When it rains it POURS! Now the main pool is dead, throwing a stratum JSON auth error.
My wallet died with the invalid checkpoint issue..
And somewhere a frog got run over by a car.
So!
My wallet died with the invalid checkpoint issue..
And somewhere a frog got run over by a car.
So!
May 03, 2014, 10:57:15 AM
And it hasn't finished syncing yet and...
"errors" : "WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers."
And.. you want this on Mintpal already? I think waiting a bit would be a good move or it could really ruin the coin....
Agreed, no rush to get on mintpal if it causes a 100 people posting here that their wallet won't sync because there is a bad actor or two out there with an old wallet still. It really seems like the wallet needs some more/better checkpoint though. I even recall someone offering to update the checkpoints.
What if you did just 5 nodes and maxconnections=5
addnode=107.170.89.103
addnode=107.170.217.4
addnode=107.170.209.91
addnode=128.199.255.146
addnode=188.226.199.223
May 03, 2014, 10:52:59 AM
RejectMining has found this error again!
"errors" : "WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers."
Lovely, working on re-sycning to get it back online now.....
Yes I noticed the dead pool in my list, my suspicion was clearly confirmed to the cause.. Fortunately I opened the wallet up and it synced in seconds. The question besides the obvious then is: How did you get a bad node connected at this point - Or would it make sense to addnodes and limit the pool itself to only a few trusted ones?
I am just throwing darts there.
May 03, 2014, 10:51:34 AM
And it hasn't finished syncing yet and...
"errors" : "WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers."
And.. you want this on Mintpal already? I think waiting a bit would be a good move or it could really ruin the coin....
May 03, 2014, 10:36:04 AM
RejectMining has found this error again!
"errors" : "WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers."
Lovely, working on re-sycning to get it back online now.....
May 03, 2014, 03:40:39 AM
Auto payouts from the official pool have stopped working.
We had to fix a couple things on the pool so APs will be temporarily off. I just tested a MP, and it worked just fine -- so if you need to, feel free to run a manual payouts until tomorrow when we turn the APs back on
May 03, 2014, 01:17:51 AM
Auto payouts from the official pool have stopped working.
May 02, 2014, 09:35:11 PM
to people having wallet synch issues...
1) download the new wallet
2) navigate to C:\Users\YOUR_PC_USERNAME\AppData\Roaming\cleanwatercoin
3) delete everything except wallet.dat file
4) create a text file named cleanwatercoin.conf
inside C:\Users\YOUR_PC_USERNAME\AppData\Roaming\cleanwatercoin folder
in this file, Use only these 2 nodes
connect=107.170.209.91
connect=107.170.89.103
5) start your wallet up and let it synch
I am on block 23403 with this conf file.
The conf file that came with the updated wallet tx fix does not work
1) download the new wallet
2) navigate to C:\Users\YOUR_PC_USERNAME\AppData\Roaming\cleanwatercoin
3) delete everything except wallet.dat file
4) create a text file named cleanwatercoin.conf
inside C:\Users\YOUR_PC_USERNAME\AppData\Roaming\cleanwatercoin folder
in this file, Use only these 2 nodes
connect=107.170.209.91
connect=107.170.89.103
5) start your wallet up and let it synch
I am on block 23403 with this conf file.
The conf file that came with the updated wallet tx fix does not work
I did this and Im stuck on block 19287 of the sync process. Any suggestions guys?
I was finding when using these 2 nodes only that occasionally it would slow down / stop but only temporarily. Perhaps try removing the .conf file before starting to see if it improves things. Seems to be working for some others here.
May 02, 2014, 09:16:03 PM
when does PoS start for this coin?
Already started - my wallet is minting like crazy!
(Coins mature after 20 days)
May 02, 2014, 09:01:38 PM
when does PoS start for this coin?
May 02, 2014, 08:42:09 PM
4. Open your new wallet folder, and Rename "cleanwatercoin -qt_4.exe" to "cleanwatercoin -qt_4 -checknode=0.exe"
I'm sorry but you are mistaken, that won't make any difference at all for 2 reasons:
1) That's not how you send a command-line option to an executable. All you have done is change the filename, try renaming it to "cleanwatercoin-qt_4 -thisdoesnothinguseful.exe" it will have just as little effect.
2) As far as I am aware there is no such command line option as -checknode=0. You may be getting confused with -checkblocks=0 which will force your wallet to check every block on startup.
If you want to run your wallet with a command line option there are a couple of ways to do this:
1) Open a command line window and navigate to the folder your executable is in, and type the following:
cleanwatercoin-qt_4.exe -checkblocks=0
(Note the -checkblocks=0 is AFTER the .exe)
2) Open a new file in notepad, type exactly the same as above and click "Save As", choose "All Files" as the file type and save it as "RunCW.bat" - put this file in the same folder as cleanwatercoin-qt_4.exe and run it. You have now created a batch file which you can create a shortcut to and run from your desktop, and change as you wish if you want to add further command-line options to your wallet's startup routine in the future.
(BTW I wouldn't recommend running your wallet with -checkblocks=0 every time as it will take a very long time to load up each time)
Doh! So I guess the -checknode=0 wasn't doing anything all along! LOL! I got that from a suggestion in IRC weeks ago.
If the -checknode=0 was useless, it must be that I kept the conf file out of my %appdata% folder that allowed me to avoid bad nodes. Where/what addresses does the wallet try to connect to if there is no conf file? Perhaps just leaving out the conf file altogether will work for most people?
If there is no conf file the wallet will just search the network for available nodes to connect to. I think the problem before was that there were too many bad nodes still transmitting forked blockchains but now that the network has grown a bit there are more 'good' nodes for the wallet to reach and so it's not a problem any more.
Jump to: