Could anyone help me?
My wallet shows that it is currently synchronizing with the network -- however, It states that it is " 0 hours behind "
As far as i can tell, all my transactions are always up to date, and i instantly receive most payments.
My first steps to diagnose the problem were too delete peers.dat , blocks folder, and chainstate folder.
After a cold re-sync, The wallet is up to date for a few minutes before it resorts back to synchrnozing with the network with a status of " 0 hours behind " ...
When hovering over the progress bar it shows - 56,920 blocks out of 470,000 have been proccessed.
Can anyone explain this issue to me ?
Mine behaves exactly the same. Version v0.10.3.4-38-gd79df3d-beta.
Grab RC1, the version is v0.10.4.0. There was a bug with downloading blocks in the previous beta
Ok thanks for the prompt response! I was under impression that RC1 was optional.
Edit: Can confirm - RC1 has resolved the issue.
Wait some longer.
I have the RC1 running since it was available. The issue did not dissapear.
Agreed, The issue is reoccuring for me. Chaeplin's instructions were a little confusing for me to follow - did it solve the issue?
Could DEV please comment on the severity of this issue? Is it simply not an issue? Not sure =/
It is something that has to be corrected in the coin itself. Amuseing to me LimeCoin dev's understood it. They decided not to do it since it requires a hard fork. I recomment the dev to read it up on the link I posted. It links over to that Limecoin.
I didn't mine LimeCoins because that issue and I don't see any future in that coin anyway (byway there a 2 different LimeCoins now so they kill themself)
DarkCoin is a bit a different story. I am not really happy with DarkCoin for a number of reasons but I know that it is a major player and gains values and so I go along with it.
Chaeplin's instruction is a workaround.
He listed all the foreign IP's coming from LiteCoin and WorldCoin that connect to DarkCoin and tells you to set your routing on your system to route those IP's into nirvana so the client doesn't sees them.
I haven't tested it yet. Busy with others. But I am confident it will work.
However in looking into the future I more liked the dev would take it serious and fix it by the next occasion.
A serious coin with such a flaw is a bit of a joke.
Worshiping a scam coin with a dev that makes death threats, can't spell and writes penis in the introduction to his coin, gives you a lot of cred
