is not running "stock" on poolside. From what I understand, and most people that have been around here long enough, Kano has
spent tons of time improving the code his pool runs on. Personally, I've never coded for a Bitcoin Mining Pool, but I can imagine
it is not something to take lightly, after all, people's payouts are at stake here. I do know enough about coding to understand, Triple
Checking the work, and Testing it before calling it good.
So, it's easy to say, so and so did it in X-amount of time, if they are running the "stock" coding. I would believe that every "stock" item in the code thats been changed, has to also be changed in the asicboost code, to be compatible with the "non-stock" code. The amount
of time to do this, is dependent on, how much has to be adapted. If a pool operator has changed very little, it would take less time, and
vise/versa.
Well lets clear some things up here about asicboost (AB).
AB has nothing to do with payments.
AB has nothing to do with poolside stats/UI/etc.
AB has nothing to do with how much or little you have touched a 'stock' pool's code
AB is all about stratum (ie. getwork, getblocktemplate, submitblock, etc. )
-CK can (and please do) over complicate my answers with more in-depth analysis/coding.
Look at CK's git commit if you want to see exactly what was all involved in his adding AB..