Post
Topic
Board Bitcoin Discussion
Re: Last Time. In small words. Why 2MB impossible. Why Soft Fork. Why SegWit First..
by
anonymoustroll420
on 02/05/2017, 11:10:26 UTC
but mallicious users are not going to move funds to segwit keys and intentionally disarm themselves.. so segwit doesnt 'fix' it
segwit doesnt even force users to move funds to segwit keys either. users can still use native keys.. so segwit doesnt 'fix' it

Fucking hell. The native key users are stuck in a 1MB block. You cannot, no matter what the op code limit is, put in enough op codes into a 1MB block to make a block that takes 10 minutes to validate. The size in bytes of the tx(es) required to do that is bigger than 1MB. They cannot quadratically spam.

If they 'disarm' themselves, then they can use the full 4MB space, and still cannot quadratically spam.

This is what the sigops limit actually do:

Node: I am validating this tx but its taking too long to validate, lets not relay it.
Miner: I crafted this block but it takes too long to validate, lets just craft a new block and mine that one.

Even with sigop's limit a miner can do this:

Miner: I crafted this block but it takes too long to validate, but I am evil so I will mine it anyway!
Nodes: No! this valid block takes too long to validate! I won't be able to validate it before the next one is found, but I have to validate it because it follows all the rules! damn it I'm going to be forked!