Quote from: CIYAM on January 26, 2016, 01:45:42 PM

Quote from: xHire on January 26, 2016, 01:32:38 PM

With BIP66, all parts of BIP62 should be fixed (except those where the malleability comes from ECDSA signatures, but those aren't relevant here as it's the sender who strives for the txid remaining the same and no one else could be affected).

I think the main issue would be if the forked alt has not updated its tx signing code (as the sender's txid could be changed without their knowledge).

By this I am referring to the low S values issue which I patched for CIYAM here: https://github.com/ciyam/ciyam/blob/master/src/crypto_keys.cpp#L531

Other than that I think that using P2SH (rather than the original multisig) is just a neater approach (it probably doesn't alter the workflow though).

Yes, I try to keep this in mind. Before including an explicit support for an altcoin, I'll have to make sure that it meets certain requirements (like supporting CLTV or non-malleability or possibly something else). Moreover, there also might be altcoins that use different hash functions or generally script encoding which should also be taken into account.

But honestly, I don't expect too many of them to include needed features. Wink