Quote from: glub0x on April 07, 2017, 04:59:06 PM

Quote from: Carlton Banks on April 07, 2017, 02:33:18 PM

Quote from: glub0x on April 07, 2017, 01:47:45 PM

2m+segwit, why not?

Because it involves doubling MAX_BLOCK_WEIGHT as well as MAX_BLOCK_SIZE.

In practice, that means 2MB + 6MB, not 1MB + 3MB (Segwit BIP 141 as proposed).

What i meant in my whole post is that asicboost looks like an important issue to resolve.
Of course segwit would solve it, but it doesn't make consensus now and it can't be activated now.
So it is probably better to just stop asicboost from working and then go back to this old debate.

After asicboost has been stop working, jihan and other won't have any mean to activate it again and they might simply go on for segwit.

Yes, I broadly agree.

But it sounds like you're saying Segwit might not have a chance, but support from miners is steadily rising, consistently above 30% for nearly a week now.

Also, stopping ASIC Boost might cut Bitmain's hashrate share significantly (assuming they're actually using it, which is not an unfair assumption). Fear of getting their blocks orphaned by >51% of miners signalling Segwit might indeed change Bitmain's mind, they'd have little choice but to start signalling Segwit too, or they'd risk losing blocks and revenue.
the

Quote from: glub0x on April 07, 2017, 04:59:06 PM

I am really preaching against myself here because i am in favor of bigger block but i do not want to arguement that here because i already done that and it gives no result...

I'm not in favour of bigger blocks, but you will have your wish, when Segwit activates. I think 4MB blocks are a danger, especially since geopolitical tensions seem to increase every day (and more and more governments are using the tension to advocate putting more controls on the internet).

But I'm willing to compromise with Segwit. If you don't think 4MB blocks will be enough today, I don't know what compromise any of us could agree to.