the segwit 'activation' itself solves nothing.
even if 99.99% of people move funds to segwit keys to DISARM themselves from causing (your buzzword buglet) quadratics. 1 person can make just 5 transactions and cause 32minutes of validation delay instead of 40 seconds
You keep saying this but it's just NOT TRUE.
This is why there is a 1MB base blocksize limit.
The old keys can spam away at their 1MB block all they want. The new keys which are 'disarmed' from quadratics can spam away at the 4MB total.
You cannot attack this way, no matter the sigop count, we could remove that limit and we probably should. Sigop limit's are only a bandaid.
You simply cannot craft a tx that takes 10 minutes to validate with only a 1MB block. And segwit isn't quadratically spammy, so 4MB is OK.
It's precisely why segwit+2MB HF was the dumbest proposal in the world. That would be quadratically attackable.
It's also one reason why BU sucks big time. They can't fix quadratics without a new address format like segwit. So they are using 'bandaids' like sigops and a 1MB transaction size limit to try solve it. None of it works, it's still quadratically spammy. When you explain this to the devs, they say that the miners would never attack the network. I beg to differ:
https://bitcointalk.org/index.php?topic=327767.0The only long term plan they have to fix this is to hardfork in segwit at a later date:
https://bitco.in/forum/threads/buip037-hardfork-segwit.1591/