diff --git a/ch08-orig.asciidoc b/ch08-orig.asciidoc index d58c1c12..6f4262dc 100644 --- a/ch08-orig.asciidoc +++ b/ch08-orig.asciidoc @@ -347,7 +347,7 @@ In block 277,316 we see that the coinbase (see <>), which The first byte, +03+, instructs the script execution engine to push the next three bytes onto the script stack (see <>). The next three bytes, +0x443b04+, are the block height encoded in little-endian format (backward, least significant byte first). Reverse the order of the bytes and the result is +0x043b44+, which is 277,316 in decimal. -The next few hexadecimal digits (+03858402062+) are used to encode an extra _nonce_ (see <>), or random value, used to find a suitable proof of work solution. +The next few hexadecimal digits (+0385840206+) are used to encode an extra _nonce_ (see <>), or random value, used to find a suitable proof of work solution. The final part of the coinbase data (+2f503253482f+) is the ASCII-encoded string +/P2SH/+, which indicates that the mining node that mined this block supports the((("pay-to-script-hash (P2SH)","coinbase data and"))) pay-to-script-hash (P2SH) improvement defined in BIP0016. The introduction of the P2SH capability required a "vote" by miners to endorse either BIP0016 or BIP0017. Those endorsing the BIP0016 implementation were to include +/P2SH/+ in their coinbase data. Those endorsing the BIP0017 implementation of P2SH were to include the string +p2sh/CHV+ in their coinbase data. The BIP0016 was elected as the winner, and many miners continued including the string +/P2SH/+ in their coinbase to indicate support for this feature.