Quote from: babbey on October 07, 2015, 01:31:51 AM

Quote from: vipgelsi on October 04, 2015, 06:47:29 PM

Quote from: vipgelsi on October 04, 2015, 01:36:24 PM

Quote from: onsightit on October 04, 2015, 12:33:28 PM

Here's a list of nodes that are on the wrong fork: (based on my debug.log file)

150.101.243.74
174.57.197.124
222.237.39.100
173.57.196.254

These are also causing the "out of sync" issue for some.

-Steve

One might be my mothers i will have to check it out today. Thanks!

Fixed.

So it turns out that one of these was one of mine... fixed; hopefully that will reduce the traffic somewhat for the network (and our data caps!!).

Steve, can you tell us if the other 2 nodes are still running? Good to be hunting them down. I only realised I was on the wrong fork when I sent coins from one wallet to the other and they hadn't arrived after almost a day...

Thanks, vipgelsl. On the BlockChain tab you can click the Network tab, then next to the client version click the node list button. We still have 3 nodes on 2.0.5, but that is over a 24 hour period (I believe).

-Steve