Quote from: d5000 on May 03, 2017, 12:09:31 AM

So the "grace period" between the Segwit activation and the 2MB activation must be as long as possible (~1 year) to correctly evaluate the danger of "full block spam" (in this case "4 MB block spam"). Edit: And the 2 MB hard fork should contain also a restriction for legacy transactions. Maybe they can be prohibited and all people owning bitcoins on non-Segwit keys have to transfer them to Segwit addresses. But we don't have to do that already when the Segwit soft fork is activated (so we don't need a hard fork then), the 2 MB hard fork 1 year later would be early enough.

What if nobody attempts to create such block in order to evaluate it? Are "we" going to spam the main network ourselves for testing purposes? In regards to forcing people into Segwit addresses: While everyone using SW keys would be an optimal future, forcing them into doing this may set a dangerous precedent.

Quote from: d5000 on May 03, 2017, 12:09:31 AM

Regarding the possible 8 MB block spam, as I have already discussed in another thread, I would support going forward slower (first go to 1,5 MB/6 MB max. after a year and then to 2 MB after 1-2 years more if everything works right).

I don't see why we'd need a potential 4 MB block (2 MB + SW) for standard transactions. The mempool would be empty for quite a while.

Quote from: franky1 on May 03, 2017, 12:33:49 AM

a native(legacy) tx of 4k txsigops is treated as 16k txsigops in core v0.14 due to the WITNESS_SCALE_FACTOR (which is 4x)

Therefore, you were wrong and I was write.

Quote from: franky1 on May 03, 2017, 12:33:49 AM

yes lauda, cludgy code can lead to semantics games which core devotee's love.

It is neither "cludgy" code nor "cludgy" mathetmatics, you just don't understand it. That's all.

Quote from: franky1 on May 03, 2017, 12:33:49 AM

but segwit still doesnt make the native keys disarmed from the 4k CPU intensive time that existed in 0.12 either
so segwit for CPU intensive purposes is no better or worse

Nobody ever claimed that it did, which makes this part of your post useless.

Quote from: franky1 on May 03, 2017, 12:33:49 AM

however there is still the 5tx's to fill the 80k issue
where it doesnt need to be 16k/tx of actual sigops.. only 4k/tx..

No. 5 legacy TX with 4k each fill up the block which is "normal" behavior today, and Segwit wouldn't change that.

Learn to admit being wrong, otherwise it's pointless for you to even attempt any kind of discussion.