I've updated 2 wallets to 2.0. Everything went fine but on block 5659047 I forked, I cant sync since then now I'm 20h behind and nothing happens. How to proceed without resyncing the whole chain for 4 days?`
01:20:50
getblockhash 5659047
01:20:50
def614b5c9920cff69150c4d65c67d83591b42d9a02a2e171c8468bd3306ae2e
here what its supposed to be on the explorer
Details for Block #5659047
Hash 0000000956b04c02d0dadc51fc139aae70f879e49948d28c0170145e2c5a98f9
Date/Time 2017-09-12 03:06:45
Do you have the full debug.log file? Can you upload it somewhere for me? Encrypt it if you want..
How many connection did you have? Were they older clients? Did you compile yourself or use my download?
For now turn off your wallets and hang tight. I will get a fresh copy of the blockchain as soon as the fork takes place. You can use that to get back up to speed quickly.
hmmm, 7 leading zeros again, i hate zeroes
This is just a PoW block. The difficulty is low.
start a new client v2.0 and try to sync from scratch on two different machines.
receive on debug.log
date connect() failed after select(): Connection refused or No route to host
any idea ?
starting with addnode command included
addnode=80.56.92.208
addnode=103.86.99.7
Just no connection to those nodes.
You can try a few others.
109.227.254.135
71.126.179.61
87.98.159.143
The fork is about 4k away. So I think we are looking about this time if not a little later tomorrow night. Stay vigilant. If you are not on the right chain, just shut off and wait. I will help you get right once the fork takes place. I have 4 clients running and watching the block explore. All have been doing very well so far. I think after the fork, these side chains should be a thing of the past... Well I hope at least..
