[Bitcoin-ml] Transaction Malleabilily Fixes

[Lucas Clemente Vella]

2017-11-13 13:29 GMT-02:00 Jared Lee Richardson <jaredr26 at gmail.com>:

> It seems that some types of malleability can still be done.  The
> person who created the transaction can still malleate it, though now
> others cannot.
>

And how transaction malleated by the signing party is worse from an
ordinary double spend? It is only a bigger problem if any signer can do it
independently from the other in a multisig transactions, is this the case?


> IMO this type of malleability also needs to be fixed with an optional
> flag or setting.  There's no reason not to allow people to know that
> their transactions can't be malleated so they can use things like
> lightning; Bitcoin Cash is in no danger of forcing people to use
> lightning though high fees, it should become an optional tool for the
> use cases that do want it.  There's many use cases that can benefit
> from Lightning's advantages even though it isn't a scaling solution.
>

An opt-in solution increases complexity, and that is precisely what is
precisely what segwit does. That is one of the reasons I dislike it: it
requires from anyone who doesn't want their transactions malleated to
change their software systems in order to forbid it. I assume the vast
majority would simply prefer their transactions not to be malleated, so
that should be the default. If someone do require transaction malleability,
for whatever reason I can't imagine, that should be the one required to
opt-in. That said, I don't believe such hypothetical need is worth the
increased complexity of simply getting rid of malleability once and for all.

-- 
Lucas Clemente Vella
lvella at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-ml/attachments/20171113/0577ce19/attachment.html>