Well back to a very simple question to bitmaintech:
Please confirm if you restricted your miner's pool choices?
I doubt that in the final analysis it will be so, but if it is, then bitcoin as a whole might be f-ed up as a result, unless it changes the POW to GPU or to POS.
I also doubt it very much. People have a long history of spreading FUD when it comes to Bitmain hardware and mining pools...
Well then I'll describe it in more detail so that people will learn why to ignore your comment.
The stratum protocol has a set of 'methods' involved in connecting to a pool and starting mining.
They do NOT include the new, undocumented, unknown 'method' Bitmain has added to the S9 called "mining.multi_version"
In CKPool we don't allow random changes/additions to the stratum protocol to "just work".
Thus the change means that until we implement a change in CKPool to ignore it, after somehow finding out somewhere what exactly it is, you can't mine on any CKPool pools.
I have no idea what other pools do, you'd have to ask them.
CKPool pools are only around 5% of the bitcoin network as far as I know, though it could be higher ... since BWPool used it at one stage and there was some talk about Bitfury considering it at one stage.
(Yes someone has pointed an S9 at 2 large CKPools)
Do you allow random changes/additions to the bitcoin protocol to "just work" on your pool?
No.
Why would you allow random changes/additions to the stratum protocol to "just work"?
As for the actual change:Bitmain's cgminer git:
https://github.com/bitmaintech/cgminerNotice any of the new code in there? No.
They are required by the cgminer license to make it available to anyone who has an S9.
What haven't they done? Type one single simple command to update the public git.
What's the usual excuse given to me by Bitmain employees each time this happens?
They're too busy, they'll get around to it later.
Too busy to type one command ... ... ... ... for code that's already compiled and live in the S9.