Should be interesting to see how it goes.
My prediction: nothing happens at all.
But to be rational about it, it comes down to a fight over wanting to do it transparently or wanting to do it more obscurely. Personally, I'll take transparent over obscure any day...
Well good to see your rational analysis is missing reality.
The comment above, which you clearly didn't read, was about miners.
cgminer supports both GBT and Stratum.
Little Luke-Jr's complaint about GBT in cgminer was that it gets too much work - when it gets work as often as Stratum does.
However, that directly equates to the statement that his miner increase transaction confirm times.
Which, I guess I also need to explain to you, is bad for BTC.
His excuse is actually that GBT sends too much data.
Since that is also exactly what that statement equates to.
If Stratum and GBT get/receive the same amount of work, then according to Little Luke-Jr, that is GBT getting too much work.
So for the good of BTC it is actually better to use cgminer Stratum than his GBT implementation since the biggest proponent of GBT says that transaction confirm times should be longer and has programmed his miner to make sure they are.
Looking at the opposite issue:
Little Luke-Jr set his miner to get the Stratum transaction list MORE OFTEN than it gets work.
Which is totally STUPID since the transaction list is static for each item of work.
Yes he really does do totally MIND NUMBINGLY STUPID things.
He also put this up as a pull request in cgminer - which of course was ignored.
Bottom line is:
If you want MANY gigabytes of transactions sent to your miner every day, then yes use GBT on cgminer.
If you don't want MANY gigabytes of transactions send to your miner every day, then yes us Stratum on cgminer.
Think about that when you consider things like 3G/4G ...
--
So, I'd actually like to know which pools have been putting bad transactions into their blocks for the last 4 years?
Did anyone actually do ANY analysis of this?
Of course there is the possibility of pools putting transactions into their blocks that could be bad, or even using their pools to attack alt-chains like Like-Jr did and GBT doesn't stop that from happening - gee I wonder why that wasn't an option in GBT.
However, any pool stupid enough to put bad transactions in their blocks, would be easy to prove that it did it and unless they LIE as well as Luke-Jr and try and cover everything up as he does, they would get caught out.
You can already do a full block analysis on any block as it is generated using an active bitcoind and a bit of code to watch the transactions that come and go and that end up in each block.
There is no trick to doing this at all.
Just requires a small amount of coding.