Quote from: chickenliver503 on February 08, 2014, 09:39:00 PM

it seem my two nodes i have been using work great with the new update 48.251.15.235 88.198.198.94 but it says i have 8 active connections.

That's normal behavior. I believe the client is coded to limit itself to 8 connections by default, unless you raise it with -maxconnections.

Quote from: Taint on February 08, 2014, 09:35:35 PM

From 'getpeerinfo' I can see that these nodes are still running the wrong version:

58.6.247.70
50.147.39.37
76.126.49.244

I suspect they're the current causes of the fork. If anyone has these in their config files, I suggest removing them. Do we have any idea who the owners are?

I'm not sure there's any way to tell exactly who is causing the fork, but my current plan is to temporarily ban nodes running the old client via IP. The downside to this is that we'll effectively cripple their connection to the network, except for any connections they have added via addnode. I'd compare it to doing surgery on a cancer patient and cutting the blood supply to the tumor, but not removing it. Short of finding the owners and getting them to update (which may be practically impossible), this is the best option we have that I can think of.