I know its hard to upgrade so many devices, but 1.0.7.1 might be too old to tolerate - at least at this stage as the network isn't big enough to do it automatically.
I say lets move forward and kick them.
To you, Tiras, Slovakia, and the others complaining about the low hash power of the pool, yes I agree- maybe we should boot the botnet off.
I don't like the fact that a botnet has basically taken over the majority of the hash power here and refuses to run the latest code, which in some cases, is dangerous, as we are really a cutting edge community here.
The biggest issue I have with this is Id hate to just kick them off so they are forced to upgrade (by issuing a mandatory that refuses old blocks) and then have them upgrade and just do it again- then we are back at square 1 for our next upgrade.
The only way we can really do this properly is to make Biblepay a partial Proof-Of-Biblehash/Proof-of-stake hybrid, in the sense that you have to stake some of your balance in order to mine. That would tend to kick off the botnets, the ones who have zero or low balances, and force the PC to re-stake old coins; it also requires a PC to create the block.
The idea here is lets say we make your (coin-age * coin-amount-staked) equal to the hash-target-boost you receive for that block. Then we would tend to reward our loyal community with solutions, and not bot nets.
I'm willing to research the solution tonight and see if we can potentially put this in testnet, as long as this can be done as a mandatory before c-cex reopens. Otherwise we should probably deal with the botnet until June and explore the option for potential future release.