The BIP 91 is going to prevent a chainsplit from the sorta conflicting segwit activation methods. And hopefully solidify the 2x part.
Through Bitcoin ABC, Bitmain, ViaBTC and several others have made it pretty cleat that they do not want segwit transactions and want to scale on chain. They will hardfork. - they will chain split away from whatever BIP 91 chain does.
It is but if only a small number of people go against it does it still count? I also wonder if the naysayers will have the nerve to actually split away and go off on their own separate chain. We will have to see.
Check out my post, SegWit can be dangerous. It might be a willing compromise but there are still very valid arguments against SegWit. Expecially with it being advertised as a blocksize increase.
Yes in fact I have heard of some of these issues before in e.g in relation to validation.I hadn't even heard of the 51% attack issue that you mention. I don't think there is a perfect solution.
A fork is what is going to happen no matter what.
The BIP 91 is going to prevent a chainsplit from the sorta conflicting segwit activation methods. And hopefully solidify the 2x part.
Through Bitcoin ABC, Bitmain, ViaBTC and several others have made it pretty cleat that they do not want segwit transactions and want to scale on chain. They will hardfork. - they will chain split away from whatever BIP 91 chain does.
OK.
what will that do to the market since every currency is linked to bitcoin? Do you think we can expect another crash?
There will be volatility.
Ohh yeah
Hashpower is going to have to make a choice, even if it is an easy one.
It is but if only a small number of people go against it does it still count? I also wonder if the naysayers will have the nerve to actually split away and go off on their own separate chain. We will have to see.
Exactly, it might be an easy choice.
I hope they do.
Check out my post, SegWit can be dangerous. It might be a willing compromise but there are still very valid arguments against SegWit. Expecially with it being advertised as a blocksize increase.
Yes in fact I have heard of some of these issues before in e.g in relation to validation.I hadn't even heard of the 51% attack issue that you mention. I don't think there is a perfect solution.
There are plenty of other ways to fix malleability problems. This is entirely a problem with the core's code.
The solution is a hardfork blocksize increase.
We will never get agreement to that though or so it seems.
Course we will!
Open source either gets used the way its users want or it rots away.
Hope so:)
Of course we are not knowing all the history.
https://steemit.com/bitcoin/@lanzate/bitcoin-segwit-improvement-or-conspiracy