<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:2017-09-22&#xA;📝 Original message:On Fri, Sep 22, 2017 at 2:54 PM, Sergio Demian Lerner via bitcoin-dev &lt;&#xA;bitcoin-dev at lists.linuxfoundation.org&gt; wrote:&#xA;&#xA;&gt; If the variable size increase is only a few bytes, then three&#xA;&gt; possibilities arise:&#xA;&gt;&#xA;&gt; - one should allow signatures to be zero padded (to reach the maximum&#xA;&gt; size) and abandon strict DER encoding&#xA;&gt;&#xA;&gt; - one should allow spare witness stack elements (to pad the size to match&#xA;&gt; the maximum size) and remove the cleanstack rule. But this is tricky&#xA;&gt; because empty stack elements must be counted as 1 byte.&#xA;&gt;&#xA;&gt; - signers must loop the generation of signatures until the signature&#xA;&gt; generated is of its maximum size.&#xA;&gt;&#xA;&#xA;Or (my preference);&#xA;&#xA;- Get rid of DER encoding alltogether and switch to fixed size signatures.&#xA;&#xA;Cheers,&#xA;&#xA;-- &#xA;Pieter&#xA;-------------- next part --------------&#xA;An HTML attachment was scrubbed...&#xA;URL: &lt;http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170922/5cb68030/attachment.html&gt;</html></oembed>