Thank you for telling me what you have posted multiple times, going so far as to quote yourself just to mention it again.
Have YOU contacted any of devs directly? Your not going to get anywhere by repeatedly spamming this thread with that idea. YOU need to reach out to them and offer to help.
Here is another thought, why don't you compile your own version of the wallet/daemon with that protocol and see if anyone else is willing to upgrade. Or, ya know, you could wait until POSv kicks in and this will be a moot point as POW blocks won't be accepted by the upgraded clients.
They would have gotten a notification for the pull request. People keep talking about forks and out of date node issues. The protocol change was made in the code and then removed, for whatever reason. So while POSV would be a nail in the old node coffin, the fact of the matter is that people can't move coin off the exchanges right now, including me. Additionally, the excitement of the changes being made, and the increased interest in supporting POT, is waning because there is no clear message being made about the issues people are reporting.
I've made a suggestion. Yes, it was numerous times... good for you for being able to keep track of things. However, I've had a vested interest in POT off and on again over the last year or so, and I'd just like to know that things are being handled properly. Fact of the matter is that using the -disablesafemode flag doesn't resolve the alleged fork issues right now, or the possibility of launching a fork attack on the chain.
Just my $0.02.
-Fuse
