Pages:
Author

Topic: Why was SegWit2X implemented in the first place? - page 2. (Read 1378 times)

legendary
Activity: 2870
Merit: 2474
https://JetCash.com
So are 2Mb blocks here then? I think larger blocks are extremely destructive to Bitcoin's future. In fact I believe that the blocksize should be halved, and generation frequency increased. I believe that it will have to happen in the future, so why not do it now.
full member
Activity: 294
Merit: 125
Alea iacta est
Was it hidden as part of the original SegWit and the core developers did not know about it?
This is pretty much what happened. They only wanted to activate segwit if segwit 2x was activated later down the road. Core knew this but there wasnt' a whole lot they could do. So in a sense the 2x was forced into the agreement because otherwise we wouldn't see segwit 1x at all.
member
Activity: 154
Merit: 11

Segwit itself had been designed and supported by the Core developers.
So when it was actually implemented they accepted it of course.

As for 2Mb blocks hard fork - firstly, after the Segwit activation it is unnecessary, it gives almost no advantages while increasing the volume of the blockchain.

Secondly, the Core team hates the unrespectful compulsory methods 2x devs chose for their venture

newbie
Activity: 7
Merit: 0
I'm familiar enough now about why the core people dislikes 2X. But, why was this accepted in the first place? Was it hidden as part of the original SegWit and the core developers did not know about it?
Pages:
Jump to: