https://nostr.ae https://nostr.ae/npub1a0x9q2pq5ccnqn5v8m6mx8hf3rgnls5gyhhryg3pqkz5fmjv0dys8hlcuw https://nostr.ae/nevent1qqsv03l5qepqwgszj2halknhku3l9rjk3jdppuja7cprc6egj6vyg5czyr4uc5pgyznrzvzw3sl0tvc7axydz07z3qj7uv3zyyzc238wf3a5j2hja4z In reply to <a href='/nevent1qqsfq8m3htptsws7cvx8pamwptj5tam53dv0knlz4lckmztnrhzre9sgtt38p'>nevent1q…t38p</a><br/>_________________________<br/><br/>📅 Original date posted:2017-05-19<br/>📝 Original message:Back in 2010, there was a bug found in Core which allowed denial-of-service<br/>attacks due to the software crashing on some machines while executing a<br/>script - see CVE-2010-537.<br/>I believe the removed (&#34;disabled&#34;) opcodes should be re-introduced along<br/>with a standardized behavior definition.<br/>For example, when execution of an opcode results in an arithmetic error,<br/>such as OP_DIV with a zero divisor, the script should exit and fail.<br/>The string splice opcodes should also check their arguments for<br/>correctness, etc.<br/><br/>These opcodes would enhance the flexibility of scripts and allow<br/>sophisticated native smart contracts to be created.<br/>-------------- next part --------------<br/>An HTML attachment was scrubbed...<br/>URL: &lt;<a href="http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170519/6209b7a2/attachment.html&gt">http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170519/6209b7a2/attachment.html&gt</a>; 2023-06-07T18:01:19Z