Post
Topic
Board Speculation
Re: Wall Observer BTC/USD - Bitcoin price movement tracking & discussion
by
CoinCube
on 22/05/2017, 13:48:23 UTC
So is it an attempt to stop the User activated fork getting traction ?

yes, because the period from august 2017 to november 2017 is the enforced period for Segwit ... not the LOCK period.
https://github.com/bitcoin/bips/blob/master/bip-0148.mediawiki

so Segwit2Mb is a trap.
they want introduce the 2Mb before SegWit LOCK.

So the folks who want 2Mb don't trust the SegWit people not to break away after SegWit is locked and block a later block size increase?

Sounds understandable given the emotionalism on this issue. It would be very disruptive to activate SegWit and then deactivate it before LOCK. Seems unlikely the miners would do this. It seems far more likely that the SegWit folks would increase their opposition to a block size increase to 2 Mb once they already have what they want.

I am not understanding why this is not a reasonable roadmap forward.

Any block size increase is not a reasonable roadmap forward. It solves nothing! It just postpones the inevitable next block size increase - 4mb, 8mb, 16mb... until full centralization. Big blocktards will accept anything just to follow this roadmap.



If it also gets SegWit activated in the process then isn't it solving something?

Increasing the block size to 2Mb is not a slippery slope. It does not necessarily follow that we will then go to 4mb, 8mb, 16mb until full centralization.