org.bitcoins.core.script.control
Checks if an OP_IF/ OP_NOTIF ScriptToken has a matching OP_ENDIF
Finds the indexes of our OP_ELSE (if it exists) and our OP_ENDIF.
Returns the first index of an OP_ENDIF.
Returns the first index of an OP_ENDIF.
Finds the last OP_ENDIF in the given script.
Returns the index of the matching OP_ENDIF for the OP_IF statement.
Evaluates the OP_ELSE operator.
Evaluates an OP_ENDIF operator.
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.
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.
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.
Marks Transaction as invalid if top stack value is not true.
Parses a list of ScriptTokens into its corresponding BinaryTree
Removes the first OP_ELSE in a BinaryTree.
Removes the first OP_ELSE expression encountered in the script.
Removes the first occurrence of OP_IF or OP_NOTIF in the BinaryTree.
Removes the first OP_IF encountered in the script.
Created by chris on 1/6/16.