<oembed><type>rich</type><version>1.0</version><author_name>npub1f2nvlx49er5c7sqa43src6ssyp6snd4qwvtkwm5avc2l84cs84esecrwet</author_name><author_url>https://nostr.ae/npub1f2nvlx49er5c7sqa43src6ssyp6snd4qwvtkwm5avc2l84cs84esecrwet</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2014-02-12&#xA;📝 Original message:On Wed, Feb 12, 2014 at 4:39 PM, Alex Morcos &lt;morcos at gmail.com&gt; wrote:&#xA;&gt; I apologize if this has been discussed many times before.&#xA;&#xA;It has been, but there are probably many people like you who have not&#xA;bothered researching who may also be curious.&#xA;&#xA;&gt; As a long term solution to malleable transactions, wouldn&#39;t it be possible&#xA;&gt; to modify the signatures to be of the entire transaction.  Why do you have&#xA;&gt; to zero out the inputs?  I can see that this would be a hard fork, and maybe&#xA;&gt; it would be somewhat tricky to extract signatures first (since you can sign&#xA;&gt; everything except the signatures), but it would seem to me that this is an&#xA;&gt; important enough change to consider making.&#xA;&#xA;Because doing so would be both unnecessary and ineffective.&#xA;&#xA;Unnecessary because we can very likely eliminate malleability without&#xA;changing what is signed. It will take time, but we have been&#xA;incrementally moving towards that, e.g. v0.8 made many kinds of&#xA;non-canonical encoding non-standard.&#xA;&#xA;Ineffective— at least as you describe it— because the signatures&#xA;_themselves_ are malleable.</html></oembed>