Re: Last Time. In small words. Why 2MB impossible. Why Soft Fork. Why SegWit First..
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).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.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.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.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.(disclaimer their is bait in my last sentence i wonder if you will bite)
Do any from both sides (I see the same posters) feel this will ever come to meet in some middle?
Why would you compromise when you've delivered an actually proven and working solution for something that has no benefits aside from a capacity increase? 