<oembed><type>rich</type><version>1.0</version><author_name>npub1tjephawh7fdf6358jufuh5eyxwauzrjqa7qn50pglee4tayc2ntqcjtl6r</author_name><author_url>https://nostr.ae/npub1tjephawh7fdf6358jufuh5eyxwauzrjqa7qn50pglee4tayc2ntqcjtl6r</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>📅 Original date posted:2015-01-21&#xA;📝 Original message:On Wed, Jan 21, 2015 at 3:37 PM, Gavin Andresen &lt;gavinandresen at gmail.com&gt; wrote:&#xA;&gt; DERSIG BIP looks great to me, just a few nit-picky changes suggested:&#xA;&gt;&#xA;&gt; You mention the &#34;DER standard&#34; : should link to&#xA;&gt; http://www.itu.int/ITU-T/studygroups/com17/languages/X.690-0207.pdf (or&#xA;&gt; whatever is best reference for DER).&#xA;&gt;&#xA;&gt; &#34;this would simplify avoiding OpenSSL in consensus implementations&#34;  --&gt;&#xA;&gt; &#34;this would make it easier for non-OpenSSL implementations&#34;&#xA;&gt;&#xA;&gt; &#34;causing opcode failure&#34;  : I know what you mean by &#34;opcode failure&#34;, but it&#xA;&gt; might be good to be more explicit.&#xA;&gt;&#xA;&gt; &#34;since v0.8.0, and nearly no transactions&#34; --&gt;  &#34;and very few&#xA;&gt; transactions...&#34;&#xA;&gt;&#xA;&gt; &#34;reducing this avenue for malleability is useful on itself as well&#34;  :&#xA;&gt; awkward English. How about just &#34;This proposal has the added benefit of&#xA;&gt; reducing transaction malleability (see BIP62).&#34;&#xA;&#xA;Nit addressed, hopefully.&#xA;&#xA;-- &#xA;Pieter</html></oembed>