Difference between revisions of "OP CODESEPARATOR"

m
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
OP_CODESEPARATOR was originally designed to be inserted between the ScriptPubKey and ScriptSig by the script evaluation engine. When OP_CHECKSIG is called in the ScriptPubKey, it will remove everything before OP_CODESEPARATOR. In this case, the entire ScriptSig will be removed. This is because ScriptSig which contains the signature is not signed by the signature.  
+
OP_CODESEPARATOR was originally designed to be inserted between the ScriptPubKey and ScriptSig by the script evaluation engine. When OP_CHECKSIG is called in the ScriptPubKey, it will remove everything before OP_CODESEPARATOR. In the default case, the entire ScriptSig will be removed as the ScriptSig containing the signature cannot be signed by the signature.  
  
There is no rule to prevent users from inserting OP_CODESEPARATOR into the ScriptPubKey. However, OP_CODESEPARATOR will only be effective if it is read by OP_CHECKSIG in the same ScriptPubKey. OP_CHECKSIG will only read the closest OP_CODESEPARATOR just before it, and remove all contents before that.  
+
There is no rule to prevent users from inserting OP_CODESEPARATOR into the ScriptPubKey however OP_CODESEPARATOR will only be effective if it is read by OP_CHECKSIG in the same ScriptPubKey. OP_CHECKSIG will read back to the closest OP_CODESEPARATOR before it and remove all message contents before that.  
  
Based on the understanding above, we can construct the following ScirptPubKey:
+
==Example==
 +
Based on the understanding above, we can construct the following ScriptPubKey:
  
 
<code>OP_CODESEPARATOR OP_CHECKSIGVERIFY OP_CODESEPARATOR OP_CHECKSIGVERIFY OP_CODESEPARATOR OP_CHECKSIG</code>
 
<code>OP_CODESEPARATOR OP_CHECKSIGVERIFY OP_CODESEPARATOR OP_CHECKSIGVERIFY OP_CODESEPARATOR OP_CHECKSIG</code>
Line 9: Line 10:
 
To unlock this ScriptPubKey, we can use the following ScriptSig:
 
To unlock this ScriptPubKey, we can use the following ScriptSig:
  
<Sig A> <PK A> <Sig B> <PK B> <Sig C> <PK C>
+
<code><Sig A> <PK A> <Sig B> <PK B> <Sig C> <PK C></code>
  
Note that the first OP_CHECKSIG will verify <Sig C> <PK C> on a message that including "OP_CHECKSIGVERIFY OP_CODESEPARATOR OP_CHECKSIGVERIFY OP_CODESEPARATOR OP_CHECKSIG".
+
Note that the first OP_CHECKSIG will verify <Sig C> <PK C> on the following message:
  
The second OP_CHECKSIG will verify <Sig B> <PK B> on a message that including "OP_CHECKSIGVERIFY OP_CODESEPARATOR OP_CHECKSIG" and excluding the first OP_CHECKSIGVERIFY.
+
<code>OP_CHECKSIGVERIFY OP_CODESEPARATOR OP_CHECKSIGVERIFY OP_CODESEPARATOR OP_CHECKSIG</code>
  
The last OP_CHECKSIG will verify <Sig A> <PK A> on a message that including " OP_CHECKSIG" and excluding the first two OP_CHECKSIGVERIFY.
+
The second OP_CHECKSIG will verify <Sig B> <PK B> on the following message:
  
If someone changes the order of the signature in the ScritSig, the verification of the signature will fail.
+
<code>OP_CHECKSIGVERIFY OP_CODESEPARATOR OP_CHECKSIG</code>
 +
 
 +
i.e. the message hash used to create the signature excludes the first OP_CHECKSIGVERIFY and the OP_CODESEPARATOR inserted by the script evaluation engine.
 +
 
 +
The third OP_CHECKSIG will verify <Sig A> <PK A> on the following message:
 +
 
 +
<code>OP_CHECKSIG</code>
 +
 
 +
i.e. the message hash used to create the signature excludes the first and second instances of OP_CHECKSIGVERIFY and OP_CODESEPARATOR.
 +
 
 +
If someone changes the order of the signature in the ScriptSig, the verification of the signature will fail.

Latest revision as of 00:30, 18 November 2020

OP_CODESEPARATOR was originally designed to be inserted between the ScriptPubKey and ScriptSig by the script evaluation engine. When OP_CHECKSIG is called in the ScriptPubKey, it will remove everything before OP_CODESEPARATOR. In the default case, the entire ScriptSig will be removed as the ScriptSig containing the signature cannot be signed by the signature.

There is no rule to prevent users from inserting OP_CODESEPARATOR into the ScriptPubKey however OP_CODESEPARATOR will only be effective if it is read by OP_CHECKSIG in the same ScriptPubKey. OP_CHECKSIG will read back to the closest OP_CODESEPARATOR before it and remove all message contents before that.

Example

Based on the understanding above, we can construct the following ScriptPubKey:

OP_CODESEPARATOR OP_CHECKSIGVERIFY OP_CODESEPARATOR OP_CHECKSIGVERIFY OP_CODESEPARATOR OP_CHECKSIG

To unlock this ScriptPubKey, we can use the following ScriptSig:

<Sig A> <PK A> <Sig B> <PK B> <Sig C> <PK C>

Note that the first OP_CHECKSIG will verify <Sig C> <PK C> on the following message:

OP_CHECKSIGVERIFY OP_CODESEPARATOR OP_CHECKSIGVERIFY OP_CODESEPARATOR OP_CHECKSIG

The second OP_CHECKSIG will verify <Sig B> <PK B> on the following message:

OP_CHECKSIGVERIFY OP_CODESEPARATOR OP_CHECKSIG

i.e. the message hash used to create the signature excludes the first OP_CHECKSIGVERIFY and the OP_CODESEPARATOR inserted by the script evaluation engine.

The third OP_CHECKSIG will verify <Sig A> <PK A> on the following message:

OP_CHECKSIG

i.e. the message hash used to create the signature excludes the first and second instances of OP_CHECKSIGVERIFY and OP_CODESEPARATOR.

If someone changes the order of the signature in the ScriptSig, the verification of the signature will fail.