Quote from: franky1 on May 02, 2017, 10:59:40 AM

Quote from: anonymoustroll420 on May 02, 2017, 10:50:38 AM

Quote from: franky1 on May 02, 2017, 10:50:01 AM

5tx's of 16k sigops thats about 40 minute validation delays.

Can't fit that many sigops in a 1MB block.

It's interesting that 1MB is the biggest size you can have without it being quadratically spammy (over 10 minutes to validate). Satoshi picked a good limit.

did you not see the whole post
CORE V 0.12 : txsigops 4k blocksigops 20k = 5 tx of 4k each

CORE V 0.14 : txsigops 16k blocksigops 80k = 5 tx of 16k each
core v0.14.. is segwit.

yep more txsigop bloat is possible due to NEW limits of 0.14.

You can't fit the data of 80,000 OP codes into a 1MB block. There is not enough space for that data. If there was, then please make a spammable TX and prove us wrong.

Anyway the txsigops limit is enforced by nodes relaying txes, and the blocksigops is enforced by miners. Evil miner can exceed the limit if he wants. It's only a 'bandaid' to the problem.