I WOULD like to see an agreement to avoid UASF, the problem is, there's no way to do a proper hard fork in 6 months, I think 1 year would be better, oh and forget about anything that isn't Bitcoin Core approved. No one on their right mind is running software for a hard fork that isn't Core approved.
The argument to avoid UASF is there is not much support for it, it divides the Bitcoin community and very likely results in pernament Bitcoin split. The SegWit2x has better support and realistic copromise to avoid the split: unmodifed SegWit from the latest Core dev team and very small increase in blocksize which proves there is nothing like 1MB4EVR. I believe such compromise is necessary and much safer than the UASF which creates a lot of havoc, uncertainity and very likely split. So far Core devs have constructive attitude, hopefully they understand a compromise is best way to solving the scalling issue and not splitting Bitcoin apart, and SegWit2x is a relistic way to accomplish it. After so long scalling debate, 6 months seems sufficient time for everybody to update, free technical help to anybody interested is planned.
If we want to do this right, miners should follow the soft fork segwit activation then a hard fork later on, anything that isn't segwit via soft fork is a mess and a scam, since it doesnt end covert asicboost.
This is addressed here:
https://github.com/btc1/bitcoin/issues/8Just few quotes from the discussion:
jgarzik: Quoting [with permission] one chip maker, Jihan Wu of Bitmain: "Asicboost is being repetitively mentioned in the reddit. Btc1 can take a very clear stance to help to ban it if community emotion desire it"
hmsln: @jgarzik Can you confirm to us that the parts of the current Segwit implementation that might hamper/prevent Asicboost will stay the same in whatever implementation is finally released by the Working Group?
Cobra-Bitcoin:@jgarzik I don't understand why you have to use such weasel words and be so pedantic. Just answer @hmsln's question with a simple yes/no answer. This isn't difficult. If you keep being suspicious, people will assume that you're going to alter Segwit in strange ways to preserve Asicboost for the financial benefit of a certain person...
jgarzik:The WG agreed to "segwit AND 2M", and that what we are focused on delivering. To the extent that current segwit disables asicboost, or not, that remains unchanged and unmodified. This issue asks the question, therefore, do additional changes need to be added, to further ban/disable/render inert asicboost.
hmsln: @jgarzik Thanks, this is the clear answer we were waiting for.
Cobra-Bitcoin: Cheers mate. I've archived this. Good to know you're still committed to blocking Asicboost. There will be hell to pay if you ever backtrack on this.