Author: Peter Todd 2017-05-22 14:09:19
Published on: 2017-05-22T14:09:19+00:00
In a Bitcoin development mailing list, Mark Boldyrev suggested reintroducing the "disabled" opcodes to enhance script flexibility and create sophisticated native smart contracts. Boldyrev believes that the removed opcodes should be reintroduced along with standardized behavior definition. He gave an example of how the script should exit and fail when execution of an opcode results in an arithmetic error, such as OP_DIV with a zero divisor. Additionally, he suggested that string splice opcodes should check their arguments for correctness. Boldyrev also mentioned that these opcodes would allow for the creation of advanced smart contracts. When asked for examples, he referred to the CHECKSEQUENCEVERIFY and his own CHECKLOCKTIMEVERIFY bip.
Updated on: 2023-06-12T00:52:51.062246+00:00