Quote from: Lauda on May 06, 2017, 12:45:56 PM

Quote from: franky1 on May 02, 2017, 11:16:01 AM

using v0.12 rules your right..
but check out 0.14 rules
80k block 16k tx

segwit makes things worse for the 1mb block

Quote from: Lauda on May 02, 2017, 10:47:49 PM

Quote

questioner2: sigops in legacy scripts count 4x toward the 80k limit

this is in validation.cpp:GetTransactionSigOpCost
-snip-
a legacy sigop counts as 4 segwit sigops
so 20k legacy sigops would fill a block

Quote from: franky1 on May 06, 2017, 12:38:08 PM

a txsigops limit of <4k in consensus header file solves the native quadratics.!!

No. You didn't even admit that you were wrong about the in-existence of the 4k limit per TX, as that's a policy rule. How sad.

thats maths cludge is CORE centric... not NETWORK consensus

from a network overview.. if pools used the 80k CONSENSUS but were not following cores CLUDGE maths.. then it does make things worse
there needs to be a proper RULE of 4k sigops that does not change.
REAL RULE. not math cludge. not implementation defined but real NETWORK consensus RULE

other implementations also have the 80k blocksigops for NETWORK CONSENSUS. meaning that due to segwit. it can make things worse.
ESPECIALLY when core removes the cludge to make a 1merkle version which they promise(but wont uphold) after the soft activation