Your newer versions are under investigation after final versions appeared to produce wrong solutions. There are suspicions that those solutions could be back engineered to working state with proper actions applied from 3rd parties.
We currently direct everyone to use previous best working software as mysteriously old versions have disappeared from your github. At the same time when we have discovered this suspicious activity.
So, this is an accusation that my miner would try to cheat the users? This is a rather large claim. You better have some proof for that. It's the opposite, I actually reduced the fee from 2.5% (OptiminerZero) to 1% only in OptiminerEquihash.
The older versions of optiminer are all on the new download site.
http://download.optiminer.pl/optiminer-equihash-2.0.0.tar.gzhttp://download.optiminer.pl/optiminer-equihash-2.1.0.tar.gzhttp://download.optiminer.pl/optiminer-equihash-2.1.1.tar.gzhttp://download.optiminer.pl/optiminer-equihash-2.1.2.tar.gzgithub does not support well the hosting of large files. That's why the files have moved.
As you know very well we do pay fees for it so we can use it as much as we like.
If it is a problem for you we can all stop using it reverting back to a modded ccminer until we can have a community miner software.
Needs create solutions and whenever there is a big need a big solution is always found. If we find ourselves without a good working miner we can always create our own.
There was no need until now.... Let me know if there is one?
Sorry, you are very wrong here. The existence of a fee does not mean you can use it like you want. You need to accept and adhere to the license to use it. What you say is like saying with a rental car you can do anything you want because you pay a rent.
If you feel like writing your own miner, go ahead.
Here is an example from log files
We thought a block was found but it was rejected by the daemon, share data: {"job":"d3a2","ip":"::ffff:x.x.x.x","port":2053,"worker":"t1xxxxxxxxxeL","height":236147,"difficulty":0.2,"shareDiff":"4596.03419805","blockDiff":1351.176112912,"blockDiffActual":1351.176112912,"blockHash":"0000007212f19755fb017650d29e3823cf44a2b5aca1cf90baa36f3152951c0f","error":{"unknown":"check coin daemon logs"}}
ERROR: CheckEquihashSolution(): invalid solution
ERROR: CheckBlockHeader(): Equihash solution invalid
Have you considered that the user might just have used the wrong hash algorithm param when connecting to the pool?