Oh ok. What is weird though is that I was still connected to 20 nodes and receiving bad headers before I resynced.
I'm now on the good chain and I am pretty sure I am connected to the same 20 nodes. (also isn't one of your node the seed node?). So it looks like I didn't ban anyone and no one banned me?
Yes true, but it is also possible my node.biblepay.org only banned you for 1-8 hours (IE one d-dos level 1 ban per bad header received) putting you on a bad fork and while we were looking at it its possible the ban expired.
Anyway I was going to say this is such a critical test, before Christmas, I think we really need to fix the chaintip issue and force a protocol upgrade to 70709, just to ensure we have a long span of uptime for all of our core masternodes.
Just a heads up everyone, I am writing the code to force a network upgrade on testnet only, so please be ready to upgrade as during the next upgrade, all the nodes will disconnect on each other if they are running a prior to 1.0.6.3 version.
It should be out in about 30 mins....