If/(when) segwit SF is abandoned/(postponed), a 2mb increase, in its simplest safe form, should be implemented. (no partisan additions)
Is that compromise?
That will buy time for a proper re-assessment for all in the Bitcoin space.
Abandon/postpone segwit sf? (How) do you think that could happen?
It could happen. (i particually speak of a soft fork. segwit HF has different connotations)
How? oh, erm..
Core could pro-actively declare segwit a work in progress undergoing rigorous testing.
Due to this extended development time, Core could propose a 2mb hard limit be implemented first, as 2mb is also on their to do list? (nothing else. no other general tweeks)
Or maybe the test net will crash the night before launch, forcing segwit release to be abandoned last miniute.
Or possibly users will become more aware of the implications of segwit SF, or fear segwit it is not fully tested yet or needed, and rise up.
Could even be that segwit coding naturally runs into bugs, leading to delays, and again. Users loose patience and fork to classic.
So, I think it could happen in many ways.
How will possibly depend on core, balls in their court atm. Or users if they get restless, or the interaction between the two, or a tech failure.
However it should be abandoned as a SF.
"90% could be against segwit, yet THEY are the ones excluded from a fully verified blockchain." That is an attack.
(if 90% want segwit, then prove it. HF)
Why is core attacking bitcoin?