Author: Aaron Voisine 2014-07-18 22:03:44
Published on: 2014-07-18T22:03:44+00:00
In a discussion on the Bitcoin-development mailing list, the topic of how to mitigate the issue of new signatures by the sender was brought up. Aaron Voisine of breadwallet.com suggested that one possible solution would be to require all signatures deterministically generate k per RFC6979, which is currently being used in breadwallet. This would not necessarily be a required change, but it could be an option to consider.Wladimir responded to a question from Mike Hearn about why rule #4, which states that any non-push operation in a scriptSig invalidates it, is special and needs to be implemented. According to Wladimir, having non-push operations in the scriptSig can lead to malleability, where multiple sequences of opcodes can evaluate to the same result. The conversation then ended with a message promoting Black Duck Code Sight, a tool that allows for easy access and search of code within enterprises.
Updated on: 2023-06-09T01:18:02.927596+00:00