Value Members

1.  object ControlOperations extends ScriptOperationFactory[ControlOperations]
2.  object ControlOperationsInterpreter extends ControlOperationsInterpreter
3.  case object OP_ELSE extends ControlOperations with Product with Serializable

   If the preceding OP_IF or OP_NOTIF or OP_ELSE was not executed then these statements are and if the preceding OP_IF or OP_NOTIF or OP_ELSE was executed then these statements are not.

4.  case object OP_ENDIF extends ControlOperations with Product with Serializable

   Ends an if/else block.

   Ends an if/else block. All blocks must end, or the transaction is invalid. An OP_ENDIF without OP_IF earlier is also invalid.

5.  case object OP_IF extends ConditionalOperation with Product with Serializable

   If the top stack value is not 0, the statements are executed.

   If the top stack value is not 0, the statements are executed. The top stack value is removed.

6.  case object OP_NOTIF extends ConditionalOperation with Product with Serializable

   If the top stack value is 0, the statements are executed.

   If the top stack value is 0, the statements are executed. The top stack value is removed.

7.  case object OP_RETURN extends ControlOperations with Product with Serializable

   Marks transaction as invalid.

   Marks transaction as invalid. A standard way of attaching extra data to transactions is to add a zero-value output with a scriptPubKey consisting of OP_RETURN followed by exactly one pushdata op. Such outputs are provably unspendable, reducing their cost to the network. Currently it is usually considered non-standard (though valid) for a transaction to have more than one OP_RETURN output or an OP_RETURN output with more than one pushdata op.

8.  case object OP_VERIFY extends ControlOperations with Product with Serializable

   Marks transaction as invalid if top stack value is not true.