...
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
Not sure why im bothering replying to you when you keep insulting me, but since you keep spouting false accusations ill further explain what's going on in the interest of being as open as possible, and correcting you since you are the one that has no idea what your talking about.
That version rolling flag should not even be enabled on the public builds, its used only for internal testing. We have a proprietary implementation internally, which that code is designed to work for our internal servers and testing. You have no idea what we do internally, nor do you even have the faintest clue why that string you pulled from our code is coded that way. If we had that flag hidden you would be none the wiser.
Stop spreading miss-information and confusing our customers. These miners do not support asicboost period, and every major pool supports non-asicboost miners.