{"type":"rich","version":"1.0","author_name":"npub1tjephawh7fdf6358jufuh5eyxwauzrjqa7qn50pglee4tayc2ntqcjtl6r","author_url":"https://nostr.ae/npub1tjephawh7fdf6358jufuh5eyxwauzrjqa7qn50pglee4tayc2ntqcjtl6r","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2017-09-22\n📝 Original message:On Fri, Sep 22, 2017 at 2:54 PM, Sergio Demian Lerner via bitcoin-dev \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e If the variable size increase is only a few bytes, then three\n\u003e possibilities arise:\n\u003e\n\u003e - one should allow signatures to be zero padded (to reach the maximum\n\u003e size) and abandon strict DER encoding\n\u003e\n\u003e - one should allow spare witness stack elements (to pad the size to match\n\u003e the maximum size) and remove the cleanstack rule. But this is tricky\n\u003e because empty stack elements must be counted as 1 byte.\n\u003e\n\u003e - signers must loop the generation of signatures until the signature\n\u003e generated is of its maximum size.\n\u003e\n\nOr (my preference);\n\n- Get rid of DER encoding alltogether and switch to fixed size signatures.\n\nCheers,\n\n-- \nPieter\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170922/5cb68030/attachment.html\u003e"}