The pools that signed the agreement just started signalling for it and it is taking off faster than any other scaling signalling. See:
https://coin.dance/blocks
Unlike the original proposal, it includes BIP91 meaning it is compatible with core's segwit now. The rapid adoption of segwit2x, which with the addition of BIP91 means that miner activated segwit is now likely on the horizon at last, and since there is overwhelming support for it and the associated 2MB hardfork in the future, that may also follow.
CK, From what you have seen over the years what do you think the activation of this would bring for the network?
Some are saying that we could possibly see a revert to 2014 / ish year difficulty drop if bitmain follow through with there "intended" plans?
What is you view on it and how do you see it being played out?
Thanks
After that people will be left scratching their heads wondering if we even need a 2MB block size increase at this time, but because all the pools made such a fuss about it, we'll have our next debate, but the pools have already insisted they want a block size increase and signed the NYA. I'm not sure how core will respond at that stage because that will be the true test of whether the miners can effect a change in consensus - but despite all the anti-core rhetoric, core dev has always overwhelmingly said they would do a block size increase but with a much slower time frame than that proposed by segwit2x simply because the regression testing required to confirm a hard fork is safe is substantial. I predict we'll get a 2MB base blocksize increase as well, though how and when I can't tell at this stage.
By the way, the current segwit2x "signalling" is just a show of support in their coinbase signature and doesn't change the way anything operates. However what it is saying is that they will be actively signalling from mid-July for segwit.