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