{"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:2014-07-18\n📝 Original message:On Fri, Jul 18, 2014 at 5:39 PM, Mike Hearn \u003cmike at plan99.net\u003e wrote:\n\u003e The rationale doesn't seem to apply to rule #4, what's so special about that\n\u003e one?\n\nNothing really. If it's controversial in any way, I'm fine with\nchanging that. It's just one those things that nobody needs, nobody\nuses, has never been standard, and shouldn't have been possible in the\nfirst place IMHO. Given that, it's easier to just make it a consensus\nrule.\n\n\u003e Although I agree not having to support all of DER is nice, in practice I\n\u003e think all implementations do and libraries to parse DER are widespread.\n\u003e Given that the last time we modified tx rules without bumping version\n\u003e numbers we managed to break the only functioning iPhone client, I've become\n\u003e a big fan of backwards compatibility: seems the default choice should be to\n\u003e preserve compatibility over technical niceness until the old versions have\n\u003e been fully phased out.\n\nI'm not comfortable with dropping OpenSSL-based signature parsing\nuntil we have well-defined rules about which encodings are valid. At\nthis point I'm not even convinced we *know* about all possible ways to\nmodify signature encodings without invalidating them.\n\nBut perhaps we should investigate how many non-DER signatures still\nmake it into blocks first...\n\n-- \nPieter"}