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