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.
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