[Bitcoin-ml] Malleability - Show of hands

[Jameson Lopp]

All it takes is a single skilled person listening to the network and
malleating all unconfirmed transactions in order to wreak havoc - I wrote
that article after having to deal with sustained third party malleability
attacks in 2015. Very few users will have the technical capability to
perform first party transaction malleation, thus it's a lower priority
concern.

On Mon, Oct 9, 2017 at 12:20 PM, Tomas via bitcoin-ml <
bitcoin-ml at lists.linuxfoundation.org> wrote:

> Hi Jameson,
>
> Thanks for your input,
>
> On Mon, Oct 9, 2017, at 17:58, Jameson Lopp via bitcoin-ml wrote:
>
> Does no one on this list operate high transaction volume wallets? There
> are a multitude of reasons that malleability fixes are desirable. Here's an
> article I wrote about it, before Segregated Witness was even a thing:
> https://blog-archive.bitgo.com/malevolent-malleability/
>
>
> I am well aware of the problems of malleability, but I don't think your
> bullet points really help.
>
> 1, 2, 5 and 6 are simple and rather silly bugs in badly written software.
> 3 isn't fixed by any malleability fix at all, as the creator of the
> transaction can *always* malleate it.
> 4 is a fair point but only effect very rare cases.
> 7 is unclear
>
> 8 is the one I would like to fix, and I am attempting to fix with this
> OP_SPENDANYOUTPUT proposal.
>
> Also note that attempting to fix 1,2,4,5,6 would require a mandatory
> malleability fix which would problems of its own.
>
> (3), and (7) are particularly interesting as they seem to stem from the
> misunderstanding that it is somehow possible to prevent the author of a
> transaction to change it.
>
> Tomas van der Wansem
>
> _______________________________________________
> bitcoin-ml mailing list
> bitcoin-ml at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-ml
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-ml/attachments/20171009/5abf53f0/attachment.html>