Quote from: cryptoanarchist on May 16, 2017, 06:39:47 AM

Quote from: Wind_FURY on May 16, 2017, 03:49:06 AM

Quote from: cryptoanarchist on May 15, 2017, 02:46:24 AM

Malleability has never been an issue except to people who imagined it to be one. Just wait for a confirmation or two.

Yes I am aware that it is not really that big of an issue. But as an improvement for the protocol it will be always good for the longterm.

Quote

Even if it was a problem, can you give a technical explanation why SegWit is required to address malleability double spends???

Segwit is required to open the network for other technologies to be developed on the network. Do you deny that Segwit improves and makes Bitcoin more secure and robust?

Why would you want to add unnecessay software?

Because Segwit is an improvement for Bitcoin making it more secure and robust. It is making the protocol open to technologies that will help make it scale and help make it better. Technologies like Schnorr signatures that will help in Bitcoin's scalability, efficiency and privacy.

We get all that in the safety of a soft fork.

Do you deny that Segwit will improves and makes Bitcoin more secure and robust?

Quote from: jbreher on May 16, 2017, 04:13:53 PM

Quote from: Wind_FURY on May 16, 2017, 03:49:06 AM

Do you deny that Segwit improves and makes Bitcoin more secure and robust?

Do you assert that SegWit makes Bitcoin more secure? If so, how?

Do you assert that SegWit makes Bitcoin more robust? If so, how?

Do you realize that after SegWit, miners may collude to roll back to non-SegWit? Do you realize that every previous SegWit then becomes a real 'anyone can spend' transaction? Do you realize that if this is done, the colluding miners may claim the value stored in these 'anyone can spend' transactions? Do you agree that this rollback/theft may be an incentive for miners to act counter to the intentions of the rest of the Bitcoin participants (whether or not sufficient to entice them to do so)? Are you at all concerned about this possibility?

I will message someone else to answer you to technically explain.