@tryphe your node doesn't seem to be running, I'm getting this a few times on the logfile
trying connection 67.35.116.81:31174 lastseen=365146.2hrs
I deleted peers.dat, used my previous chain with block @170980 wrong fork
run the clam-qt as you instructed with -rescan -reindex and it still perform like before...
it is continuing to 171046 and stuck (still downloading, perhaps trying to figure out the best fork)
currently with 13 active connections, never drop below 10
I think there are still a few (probably many) nodes running on the wrong fork, and my client keeps connecting to them
what is the use of data inside "txleveldb" dir? I was thinking maybe something left over here that makes it advance to 171046
it keeps downloading data from nodes (by looking at my network activity) but the block stuck at 171046
I'm gonna try let it run and hopefully it fixes itself without actually re-downloading the whole chain without warning to me
is there a way to figure out or indication when my client starts reconnecting to the correct chain?
where can I see that... other than checking my best block hash & comparing with khash