Topic: [Donated $2k+ To Charity] Clean Water Coin: A Crypto Charity (Pure PoS) - page 22. (Read 195747 times)

something about bittrex?
isnt water in monday delete list?

I am very happy how this project is going.

Thanks, after some tweaking I got it syncing up to the last block.

Can you please update the 1st page with the new wallet, .conf and whatever new updates there are. Maybe main webpage also? It would help some. I can not get wallet to sync and pool or whole network went down yesterday. Thanks

The pool was finding blocks, it just had a front-end MPOS issue for the stats page. 

seem like all goes fine, but 10+ hours delay a bit scary)
oh, my vote to scrypt
dying thing is better than death born. just my opinion, no offence

transactions - not confirmed
last block found - 87944 04/07 00:37:01
pool statistics - FATAL ERROR #500

how can i solve my problem?

wallet works pretty fine, but dat pool.

According to this http://explorer.cleanwatercoin.org/t/A9ZdoMqkHH the transaction went through. I am sorry to say this, but I believe that since your transaction went through, you should have posted that everything worked out fine and the "problem" has been resolved. Instead you let it here, making me look over transactions, blocks, following the chain, in order to find out what could go wrong.

To answer your question now... From the transaction details you will find in the link I pasted, you will see that you tried to move almost the entire amount that you had available (most probably 1 block wasn't confirmed at the time). You did not calculate the charity fees though. The "Not yet redeemed" means  that your wallet was trying to spend coins that were created from a block that hasn't mature yet. And this is exactly the case: The wallet tried to find some coins for the charity fees and the only transaction it had left, was the block creation transaction that didn't mature yet, thus the message.

What makes you think it's down or on the wrong blockchain?

Mindfox, or anyone! I need a little help with a problem please - I started a fresh wallet and solo mined 13 blocks. The balance of the wallet is showing as around 11,600 WATER. However, when I tried to send coins I get:

"Error, the transaction was rejected. This might happen if some of your coins were already spent, such as if you used a copy of wallet.dat and coins were spent in the copy but not marked as spent here."

This is a brand new, fresh wallet - not a copy of an old wallet.dat

All the mined blocks are confirmed 200+ times and are showing in the block explorer - however they say "not yet redeemed" - what does this mean? Does this matter?

Here is one of the txids: caf992067db1916c6c4726c2b3ac559a9cee41cd50fae6b178169104eaa74095

Can anyone shed some light on this please and suggest how I can successfully send these coins?

off pool is down? again wrong blockchain?

Yes, the ban is IP based and it's the same as in every known wallet running, including bitcoin. So, if you change your IP, you overcome that obstacle.
Deleting peers.dat will only allow *your* wallet to connect to previously banned wallets (understand that as wallets are banning you for broadcasting too many wrong blocks, you do the exact same thing for them, when they try to give you their blocks)

About the 24 hour ban period.  I'm clueless as to how this works.  Is it an IP ban?  I mean, could I get around it by connecting from a different IP address or changing my IP address?  Could I just delete peers.dat?  Thanks

I should mention that my wallet is synced fine, this is just a theoretical question.

Delete everything (besides wallet.dat), wait for a day, then connect again

Since you know how it works, you should also know (or read the posts I made earlier) that if that's the case, you have to wait for at least a day before trying to reconnect, so that the ban period expires.
And you'll do that *after* you delete everything from your folder, with the exception of wallet.dat

Hard Checkpoints (built in the code) can't be in steps of 3 or 4. And it has nothing to do with the conf file, you must be confusing things. New wallet has disabled irc connections (which allowed any node to connect, no matter if they were banned or not). Now the first nodes are the official ones and from them, the wallet learns connectable nodes that are allowed to connect to the network (have no penalty).
If you have your old peers.dat, or if in your conf you have "irc=1" somewhere, then you will connect to any node, banned or not.

YouIsPeng - the wallet is not syncing because as I said numerous times, most probably you are banned from many nodes and you have in your peers.dat nodes that are in the wrong fork.

1.7.0.2 sync'ed
mining is ok via off pool
just waiting bittrex up

While syncing (at least trying to), I got the following error:

WARNING: Invalid checkpoint found! Displayed transactions may not be correct! You may need to upgrade, or notify developers.

Feel free to just ADDNODE the doabitofgood.com public facing peering server:

addnode=204.246.67.106:9340

getinfo currently showing:

    "blocks" : 87558,
    "connections" : 34,

Peers are all over the map, but we have solid support for the chain:

./cleanwatercoind getpeerinfo | grep heig
        "startingheight" : 83320,
        "startingheight" : 83320,
        "startingheight" : 83320,
        "startingheight" : 83323,
        "startingheight" : 68367,
        "startingheight" : 83363,
        "startingheight" : 8815,
        "startingheight" : 937,
        "startingheight" : 84265,
        "startingheight" : 84354,
        "startingheight" : 84609,
        "startingheight" : 84713,
        "startingheight" : 84780,
        "startingheight" : 84808,
        "startingheight" : 85461,
        "startingheight" : 86722,
        "startingheight" : 8499,
        "startingheight" : 8874,
        "startingheight" : 83113,
        "startingheight" : 87046,
        "startingheight" : 8038,
        "startingheight" : 85515,
        "startingheight" : 83102,
        "startingheight" : 87270,
        "startingheight" : 87341,
        "startingheight" : 68408,
        "startingheight" : 64082,
        "startingheight" : 85600,
        "startingheight" : 87533,
        "startingheight" : 87537,
        "startingheight" : 87546,
        "startingheight" : 87549,
        "startingheight" : 87555,
        "startingheight" : 1000,

Sincerely,

David V Duccini
Executive Director
doabitofgood.com

Maybe I am lucky, but I have 0 issues with 1.7.0.1

synchs and stakes perfectly for me since the beginning

BTW, before anyone suggests it I am fully aware that I can go through and cherry pick the nodes that seem to be on the correct chain then use connect= to force the wallet to connect only to them.

I was under the impression that this new wallet was supposed to have built-in checkpoints to avoid having to go through all this crap again. If you go back about 50 pages in the thread we spent weeks trying to find a .conf file that would sync the wallets properly.

Mindfox - why isn't the wallet syncing now??