{"type":"rich","version":"1.0","author_name":"npub1dw88wd5gqsqn6ufxhf9h03uk8087l7gfzdtez5csjlt6pupu4pwsj8plrw","author_url":"https://nostr.ae/npub1dw88wd5gqsqn6ufxhf9h03uk8087l7gfzdtez5csjlt6pupu4pwsj8plrw","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2019-03-07\n📝 Original message:\u003e * OP_CODESEPARATOR in non-BIP 143 scripts fails the script validation.\n\u003e This includes OP_CODESEPARATORs in unexecuted branches of if statements,\n\u003e similar to other disabled opcodes, but unlike OP_RETURN.\n\u003e\n\nOP_CODESEPARATOR is the only mechanism available that allows users to sign\nwhich particular branch they are authorizing for within scripts that have\nmultiple possible conditions that reuse the same public key.  Because of\nP2SH you cannot know that no one is currently using this feature.\nActivating a soft-fork as describe above means these sorts of funds would\nbe permanently lost.  It is not acceptable to risk people's money like this.\n\nI suggest an alternative whereby the execution of OP_CODESEPARATOR\nincreases the transactions weight suitably as to temper the vulnerability\ncaused by it.  Alternatively there could be some sort of limit (maybe 1) on\nthe maximum number of OP_CODESEPARATORs allowed to be executed per script,\nbut that would require an argument as to why exceeding that limit isn't\nreasonable.\n\n-- \nRussell O'Connor\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20190307/0f0ed246/attachment.html\u003e"}