You are just making shit up.
Why implement or attempt to implement some kind of change to bitcoin that is not needed and may even cause damage (because it is not needed) merely because some know nothings are hypothesizing that such a change is needed?
I think that there is plenty of understanding that we gotta see how seg wit plays out first before adding some new and unjustified layer.
Luke will give the HF over to antpool in July. What remains to be seen is will he include segwit with the HF code or not? If not , than will antpool create a new implementation and pay some other developer to fork the main branch and include the 2MB HF with segwit (3.8 to 4MB average capacity)? The Irony is the person delivering the 2MB HF code is the person that would prefer the miners to set a blocksize limit of 0.5MB now.
What do I assume will happen? Luke will indeed fulfill his end of the bargain as he is an honest and honorable man, But my guess* is he will include a free second HF version(Keccek SHA 3 ) that could be used as an option if the community decides to.
https://github.com/luke-jr/bitcoin/commit/8d3a84c242598ef3cdc733e99dddebfecdad84a6Of course the miners and the community can decide what version they prefer or write their own as this is not a decision for developers to make.
Fun times ahead.
*Backup guess = the HF code offered will include Tonal Support and automatically include hashed scripture messages within all txs with prayers to Saint Matthew and as a convenience detect and ignore all txs involved in gambling.
