even activating segwit does not stop worrying about O(n^2) attacks!!
people wanting to cause O(n^2) attacks will still do O(n^2) attacks
wake up to reality.
O(n^2) attacks are only allievated by those using segwit keys.. the thing you need to understand is attackers wont use those keys even after activation. so the problem is not solved.
You are thinking about this completely wrong. Let's revisit:people wanting to cause O(n^2) attacks will still do O(n^2) attacks
wake up to reality.
O(n^2) attacks are only allievated by those using segwit keys.. the thing you need to understand is attackers wont use those keys even after activation. so the problem is not solved.
We know that at 1 MB that quadratic hashing problem is *okay* (to put in this way) and that it opens a DOS attack vector at higher block sizes. I think we can agree on this statement. If people create Segwit TXs, they can create blocks that are bigger than 1 MB. However, in this case the O(n^2) is reduced to O(n) which levitates the problem.
So what does happen if someone chooses to not use Segwit 'keys' and decides to create extremely expensive transactions? Nothing, they still can't create a TX/block that it significantly (or adequately) bigger in order for the 'attack' to work.
Until core does that hard fork to increase 'blocksize' they said they were going to do
