Closed Comodore125 closed 8 years ago
Did you try to delete peers.dat before relaunching?
It did not help.
Please send your debug.log to holger@dash.org
done
Please update to
https://dashpay.atlassian.net/builds/browse/DASHW-DEV-498/artifact/JOB1/gitian-win-dash-dist/
and add these nodes to your dash.conf
addnode=[2001:1608:10:25:10::101e:7241]:19999
addnode=[2001:1608:10:25:10::10d2:f4d1]:19999
addnode=[2001:1608:45:3::242:ac11:2]:19999
addnode=[2001:1608:45:3::242:ac11:3]:19999
addnode=[2001:1608:45:3::242:ac11:4]:19999
addnode=[2001:1608:45:3::242:ac11:5]:19999
addnode=[2001:1608:45:3::242:ac11:6]:19999
addnode=[2001:1608:45:3::242:ac11:7]:19999
addnode=[2001:19f0:9000:2042::2]:19999
addnode=[2001:19f0:9000:2049::2]:19999
I had similar problem, i was forked, deleted all folders and files from testnet3 and restarted and let it sync, all good.
How many blocks are necessary to keep wallet stuck with wrong chain? This seems to be an issue with consensus protocol. Probably in bitcoin this issue persists as well.
This is not a issue with the consensus protocol, it only applies to Dash testnet where only 20 CPU cores are mining and you can fork the network by running a single rough GPU miner :)
Is your sync problem solved?
Yes, by deleting the blockchain, I already had last build.
I have all required peers with latest build on testnet. (win10x64)
I already tried -reindex