Which is probably why 95% sustained segwit activation signaling is needed. It's uglier and more dangerous than a coordinated hard fork.
95% is just about network ORPHAN risk(of ~5%) that is all its about.... reducing orphan risk between the pools.
(separately, user nodes could still reject blocks by recognising a certain block version and reject it and cause more orphans, if they so chose to)
not about getting to 95% new feature benefit.
even after activation segwit doesnt offer any fix.
it requires USERNODES to update to yet another new (not yet released) version.
AND THEN (separate requirement) users to voluntarily move funds from native priv/pub key to segwit priv/pub keys and only use segwit keys for.. wait for it.. for only those segwit KEY users to be disarmed from the issues of those users being able to make sigop bloat/malleated tx.
while still not dealing with those that stay with native keys(even using segwit as just a node)
like i explained at the bottom of post #5 above about if 50% of users using segwit keys causes a 50% possible boost to tx count... but knowing malicious users will not use segwit keys.. wont be even help one bit with sigop quadratic spam/malleation