v2.2.0 binaries were built before that commit.
That hardened checkpoint was added 26 days ago. 2 days after 2.2.0. So why was the checkpoint added 2 days after the 2.2.0 release and sat there for 26 days before you released the 2.2.1 client. Your 2.2.0 client really did a whole heap of nothing and to release a client without a checkpoint update is amateur at best. Shit you guys just realised how to put in stake modifiers, after 2 years ROFL.
So for anyone to claim that the 2.2.0 is the correct chain is wrong, to deny their is a massive big fork out there is wrong.
Blundertoe honestly, if you need this shit done right just ask. Ill do it cheaper than these cowboys thats for sure.
EDIT: You might want to explain checkpoints to @vancefox
I don't need an explanation... not all of us (you) have a hard time figuring out things...
I didn't have a single problem with 2.2.0 which ran up till today. I upgraded to 2.2.1 today with a complete fresh install without a problem...
Remember, whenever you point the finger at someone three are pointing right at the real problem.
Your lack of knowledge and understanding have made TEK look like a bit of a joke. I hope your not involved in the team because really you have no idea.
I was willing to back TEK 100%, stake and follow it. Now I know you have two chumps in here calling shit wrong and for that I dumped.
Blundertoe I thought you had shit in control here but an unpatched 9000 block fork is not great at all.
And Vancefox, I lol and lol some more. Did you find out what a checkpoint is yet?
First I like to thank you for dumping , so that I could buy cheap
Next if you dun like it here , please leave since you already sold out
Last noise23 has been doing a great job for free , has saved other coins before . So if you looking for a job go beg at other coin unless you can contribute for free , which is the going rate for noise23 work.
Ps . I'll support any coin if noise23 is one of devs, thanks for great job noise23