This is what BIP109 fixes and why 2 MB hard fork is usefull to be activated as soon as possible. For more info why reducing to 1.3 GB Signature operations in BIP109 2 MB hard fork used by Bitcoin Classic is necessary:
http://8btc.com/forum.php?mod=viewthread&tid=29511&page=1#pid374998The worst case block validation costs that I know of for a 2.2 GHz CPU for the status quo, SegWit SF, and the Classic 2 MB HF (BIP109) are as follows (estimated):
1 MB (status quo): 2 minutes 30 seconds (19.1 GB hashed)
1 MB + SegWit: 2 minutes 30 seconds (19.1 GB hashed)
2 MB Classic HF: 10 seconds (1.3 GB hashed)
SegWit makes it possible to create transactions that don't hash a lot of data, but it does not make it impossible to create transactions that do hash a lot of data.
Hmm, the link took me to a whole lot of Asian looking characters; am I meant to use a translator? As such I couldn't find the quoted material.
Question: Can the BIP109 magic be applied if we have the 1MB block size limit? If not, why not?