diff options
| author | Chris Stewart <stewart.chris1234@gmail.com> | 2017-01-03 17:46:14 -0600 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-01-03 17:46:14 -0600 |
| commit | 608d5dc95f2ddcee32758fe73de6d68b99021e39 (patch) | |
| tree | c6ac6496087a9e01529d0cf51a9ec33897e4957e | |
| parent | d84186c01caa6728aff157b596908e8c5fdd2ad0 (diff) | |
Update bip-0141.mediawiki
Clarifying rewording, `OP_0` is not a 1 byte push op code since it pushes the empty byte vector onto the stack.
| -rw-r--r-- | bip-0141.mediawiki | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/bip-0141.mediawiki b/bip-0141.mediawiki index cbdf5ce..eeb6eb9 100644 --- a/bip-0141.mediawiki +++ b/bip-0141.mediawiki @@ -83,7 +83,7 @@ If all transactions in a block do not have witness data, the commitment is optio === Witness program === -A <code>scriptPubKey</code> (or <code>redeemScript</code> as defined in BIP16/P2SH) that consists of a valid 1-byte push opcode (<code>OP_0,OP_1,OP_2...,OP_16</code>) followed by a data push between 2 and 40 bytes gets a new special meaning. The value of the first push is called the "version byte". The following byte vector pushed is called the "witness program". +A <code>scriptPubKey</code> (or <code>redeemScript</code> as defined in BIP16/P2SH) that consists of a select subset of opcodes (<code>OP_0,OP_1,OP_2,...,OP_16</code>) followed by a data push between 2 and 40 bytes gets a new special meaning. The value of the first push is called the "version byte". The following byte vector pushed is called the "witness program". There are two cases in which witness validation logic are triggered. Each case determines the location of the witness version byte and program, as well as the form of the scriptSig: # Triggered by a <code>scriptPubKey</code> that is exactly a push of a version byte, plus a push of a witness program. The scriptSig must be exactly empty or validation fails. (''"native witness program"'') |