...
Not sure how else to explain it to you, rolling version ASICBOOST is not supported on the hardware so there is no reason to work on this codebase until it is supported by the ASICs themselves....
The code's ability to handle asicboost is what matters.
Versions sent and received work, but alas with a bug.
Getting any performance gain using asicboost is not relevant.
I've already given you the bug fix to your code so I've no idea why you wont implement it.
There are cases where the miner needs to be able to handle asicboost because not every mining target on the planet supports both: on and off.
With the
VERY simple fix added, that issue disappears, the person running an apollo can have it turned on or off as required.
Though I will quote you that probably explains you have no idea what you are talking about:
...
There is no bug, the miner supports version rolling for new ASICs but its not implemented in the current ASIC hardware. This is why you are seeing incorrect version data.
No, it's using the wrong display of the version data - %x - instead it should be the equivalent of %08x