Author

Topic: On the wrong fork, peers.dat (Read 891 times)

sr. member
Activity: 637
Merit: 250
November 08, 2015, 06:10:54 PM
#5
What version/client?  I had a mac armory client that would get stuck on a fork block and had to upgrade to get past.
Litedoge. Works a treat now.
member
Activity: 102
Merit: 10
November 08, 2015, 03:45:31 PM
#4
What version/client?  I had a mac armory client that would get stuck on a fork block and had to upgrade to get past.
sr. member
Activity: 637
Merit: 250
November 07, 2015, 04:29:35 PM
#3
It should. You can also delete all of the blk.dat files to do that you start with a clean sync. You can also try using addnodes instead of deleting the peers.dat file.
That's kinda what I wanted to hear. 
Thanks very much, you're a star.
 Smiley Smiley
staff
Activity: 3458
Merit: 6793
Just writing some code
November 07, 2015, 02:13:27 PM
#2
It should. You can also delete all of the blk.dat files to do that you start with a clean sync. You can also try using addnodes instead of deleting the peers.dat file.
sr. member
Activity: 637
Merit: 250
November 07, 2015, 01:58:16 PM
#1
With a mac wallet, if I find myself on the wrong fork would deleting the 'peers.dat' file work to get onto the right fork? 
There isn't a replacement peers.dat file but i imagine firing up the wallet it would create a new peers.dat file once it had found a connection.
Jump to: