Re: New transaction malleability attack wave? Another stresstest?
Splitting the "chain" to a "binary tree" just adds more fun 
This is also the correct way to do it.
Quote
I do not see any benefits for me running it.
Perhaps to remind the community not to rely on chains of unconfirmed txs.
Btw, I wonder if it is possible to design scripts immune to this attack, e.g.
Code:
OP_SIZE 73 OP_EQUALVERIFY OP_CHECKSIG
The wallet software needs to "mine" a 73byte sig (not very hard).
The malleated sig is always 1 byte bigger, so cannot be used.