I'm having a lot of issues with my wallet updating. I tried following the steps suggested by the dev and nothing. Finally I renamed my Version folder (to Version_BU) launched the new waller and it created a new directory for everything and I did connect node etc and I still get stuck at block 70000
At this point im stuck and confued cause I pretty much did a fresh/clean install
The coin has not been completely fixed yet, don't worry about it. There are multiple forks of the chain, and the devs are still trying to fix the problems. Follow this thread and download the new wallet when they announce it, but until then, don't bother syncing or mining.
I apologize for not posting for that long, but I haven't talked to staycrypto since last update's release time.
From what I can understand from the endless debug logs I have created during that time, the problem is heavily connected with PoS blocks and how they are announced to and gets accepted by peers. I noticed that my wallet has many rejects to the PoS blocks announced by others. I believe the same happens to my wallet's PoS blocks announced to peers connected with me. This forces the wallet to keep relaying the transactions that created them until it get's banned by the connected pears. That's when wallet starts crawling to death, most probably because of the many reorganization and re-transmitting of those blocks.
That of course happens to wallets with many many blocks that have reached PoS maturity (either from mining or from transactions).
I'm posting this so I can share my suspicions and let anyone know that (at least I) still investigating and pinpointing the problem.
I've been solo mining with the new client and having some success:
1. "set generate true" works in the client. (CPU mining)
2. Pointing cgminer directly at the daemon does NOT work. Everything is rejected.
3. Putting stratum server between cgminer and the daemon works.
(
https://github.com/Crypto-Expert/stratum-mining.git)
The chain I'm on is at a height of 116170 with difficulty at 700 and rising slowly. I have 35 connected peers all running v0.8.9.9. They are confirming my blocks and I am confirming their blocks. For a while, blocks were so fast that my blocks were always orphaned. But now things are slow enough that some of mine stick. I've had some Proof of Stake blocks too (which are "mined" by the client) and they've been confirmed by others. The seed node specified by StayCrypto is one of my peers and it has not banned me.
Is anyone else on a different chain? Run this in the debug console to confirm:
> getblockhash 116170
000000000037e5b31ddd26d24b9abe3739c89acbad6efa5cf4ee1be3acacf2e6
Mindfox, so I'm not noticing this problem. Can you give me something to search for in the debug log. What does "rejects to the PoS blocks announced by others" look like in the log?
We are on the same chain because I have re-downloaded so many times the blocchain, exported wallet's address and re-created wallet.dat.
If you had many blocks mined (as usually happens in a pool's wallet) (not some and not slowly, as it happens with current hashrate of the network) you would have the problems I'm describing.
A sample log entry would be:
"ERROR: CheckProofOfStake() : INFO: check kernel failed on coinstake [hash[, hashProof=[posdiff]"
Also, you should see somewhere a REORGANIZE in your log. You'll notice that it is reorganizing 1, maby 2 or 3 blocks.
In my case, those blocks were up to 22000 or more, which resulted in DB Exception error (same thing was reported by a windows wallet if I remember correctly).
The DB_CONFIG was just a small slow-down for the error to appear, but eventually it will appear if you have many PoS blocks.