In my previous post (https://steemit.com/bitcoin/@firemonkey/is-the-support-for-segwit2x-getting-less) I gave a list of miners who do not support SegWit2x. Since then there has been a slight increase in the support for SegWit2x. Next to F2Pool also ConnectBTC is now signalling support for SegWit2x.
SlushPool is the biggest miner not signalling support. Their individual miners are allowed to make their own choices with respect to signalling but so far I have not seen a single block from slushpool that signalled support for SegWit2x.
Kano CKPool is also not signalling support and this is what they say:
"I don't need to signal anything - the pool is only 1.5% so has no effect on the majority. All I need to do is have the pool code support generating blocks for the majority mining network if any change occurs. Segwit/Segwit2x is bad for bitcoin - but if the vast majority of miners accept it, then that's what bitcoin is.". This makes sense but it is a rather passive approach. Probably the other mining pools that do not signal support have a similar view.
Currently well above 80% of the miners are signalling support for SegWit2x. The bitcoin miners say that by design the miners decide what bitcoin improval proposals are going to be implemented. That is correct, the miners are in the lead, but in the end the market will decide what will happen. The market determines how much a branche of the bitcoin blockchain is worth and the market is created by the entire community: all bitcoin owners, the exchanges, the wallet providers and the businesses who accept bitcoin.
The miner support for SegWit2x seems sufficient for implementation of SegWit on the first of august. If a UASF however gets massive support in the market the miners will have to follow.
Conclusion: It is still not clear what will happen on the first of august.