Quote from: tf2honeybadger on February 09, 2014, 03:39:12 PM

Quote from: Momiji on February 09, 2014, 03:19:56 PM

addnode=148.251.15.235
addnode=88.198.198.94

Two nodes of the most secured ones, tf2honeybadger`s

I actually don't own either of those. I think they might be wzttide's nodes. Either way, my suggestion for running a stable node is to not use ANY addnodes at all. My node (184.154.116.146/cga.inceptioncraft.net) and s4w3d0ff node are hardcoded into the client, and you will connect to them to get more peers automatically. If you just connect to us, you should be good.

Is there anyone else out there reading this who could help s4w3d0ff and me fix this forking? Banning nodes evidently did not work. I slept on the problem last night and now I'm thinking that realistically, the client is probably intermittently creating forks when a certain condition is met. I'm not certain what this could be, but I'm walking through the code to troubleshoot what it could be.

TL;DR: The best way to secure your node right now is to avoid using addnodes in your configuration file. Get rid of them and let the client get peers from s4w3d0ff and myself automatically.

Additionally, I will vouch for wzttide's trustworthiness as an escrow service. He's been a great asset to the community by running a very stable pool and giving bounties out of his own balance.

Done! I was pulling my hair out with these forks! Thanks!!