Post
Topic
Board Bitcoin Discussion
Re: Last Time. In small words. Why 2MB impossible. Why Soft Fork. Why SegWit First..
by
franky1
on 02/05/2017, 11:16:01 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.
using v0.12 rules your right..
but check out 0.14 rules
80k block 16k tx

segwit makes things worse for the 1mb block


If they 'disarm' themselves, then they can use the full 4MB space, and still cannot quadratically spam.
by filling the 1mb with spam.. then the other 3mb remains empty. because you cant stick your segwit ass in the 3mb area if you cant even get your head in the 1mb area due to the spam that has filled the 1mb area to stop anything else getting in.

its not about filling 4mb of sigop spam..
its just about being malicious with the baseblock so that the other 3mb is never utilised by only having to mess with the base block

the solution is simple

txsigoplimit 2000.

everyone wins (apart from malicious spammers)
trying to assume the solution is 'lets hope everyone including malicious users use segwit keys' is a laugh