Quote from: Lauda on May 05, 2017, 11:14:35 AM

Quote from: franky1 on May 05, 2017, 10:20:04 AM

emphasis the quadratic/cpu intensive time only happens once for a pool. when it first gets relayed a tx and validates it to add it to mempool.. the creation of a raw block is just collating data minutes later. not revalidating tx's again

If you didn't mine the block, you are going to validate it. If a malicious miner starts deploying quadratic intensive blocks at higher MB (e.g. 2 MB), they could make you constantly be behind them (hence DDOS).

now your starting to see why segwit hasnt fixed it!!

Quote from: Lauda on May 05, 2017, 11:14:35 AM

Quote from: franky1 on May 05, 2017, 10:20:04 AM

also segwit is "supposedly" 75% cheaper. which means pools get 4x less bonus from a segwit tx.

There is a reason for that. You need to re-read what Segwit is about.

core have already removed the FEE calculation features such as priority, reactive.. nothing to stop them removing the 4x witness scale factor as soon as segwit is activated.. after duping people into activating it..
maybe you need to read the documentation and code and then think of the long term.. not the temporary sales pitch..

Quote from: Lauda on May 05, 2017, 11:14:35 AM

Quote from: franky1 on May 05, 2017, 10:20:04 AM

theres also issues of if they add segwit tx's they have to form the 2 merkle. and then have some peers request the pool to strip it down to just the base block..(old nodes connected to pools)*

That's not an issue.

because of the tier network preventing old nodes connecting direct to pools, i did * that to say i was baiting you.. i was hoping you would have honesty /integrity to explain why its not an issue.. but you love to hide the bad bits under the rug with empty replies or wrong, irrelevant, not an issue

Quote from: Lauda on May 05, 2017, 11:14:35 AM

Quote from: franky1 on May 05, 2017, 10:20:04 AM

very simple keep sigops at a REAL 4k or below 4k per tx.

Which also makes it easier to clutter up blocks to hit the max sigops per block limit. As you'd say it, this is no fix.

actually you need to think deeper.. by reducing tx sigops to say 1k and then having 80k blocksigops. without any cludgy maths of pretend counting..
it changes it from being just 5-7 tx to being 80tx to fill a block.

Quote from: Lauda on May 05, 2017, 11:14:35 AM

Quote from: franky1 on May 05, 2017, 10:20:04 AM

P.S if segwit went soft first and then removed the cludge to go to 1 merkle after. that means removing the 'witness discount' which then would bring back the quadratics risk of REAL 16k sigops (8min native validation time)
(disclaimer their is bait in my last sentence i wonder if you will bite)

Your disclaimer is full of nonsense and proof that you don't understand Segwit. Go back to school.

my disclaimer was to await your reply to see how practical, critical, and honest you would be .. but you stayed silent by just saying "t does not matter" without explaining why. knowing you would dig yourself a hole should you explain

but atleast in a few area's you are starting to think beyond the temporary promotion.. now you really need to start wearing the critical hat more often and look passed the blockstream defense you keep trying to promote