From 11382984c6bb1480d85cfadcdea1edac77d9a217 Mon Sep 17 00:00:00 2001 From: "myarbrough@oreilly.com" Date: Wed, 5 Nov 2014 09:17:03 -0800 Subject: [PATCH] Made changes to ch08.asciidoc --- ch08.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ch08.asciidoc b/ch08.asciidoc index d34f6d58..59bd1307 100644 --- a/ch08.asciidoc +++ b/ch08.asciidoc @@ -338,7 +338,7 @@ In a generation transaction, the first two fields are set to values that do not ==== Coinbase Data -Generation transactions do not have an unlocking script (a.k.a. +scriptSig+) field. Instead, this field is replaced by coinbase data, which must be between 2 and 100 bytes. Except for the first few bytes, the rest of the coinbase data can be used by miners in any way they want; it is arbitrary data. +Generation transactions do not have an unlocking script (a.k.a., +scriptSig+) field. Instead, this field is replaced by coinbase data, which must be between 2 and 100 bytes. Except for the first few bytes, the rest of the coinbase data can be used by miners in any way they want; it is arbitrary data. In the genesis block, for example, Satoshi Nakamoto added the text "The Times 03/Jan/2009 Chancellor on brink of second bailout for banks" in the coinbase data, using it as a proof of the date and to convey a message. Currently, miners use the coinbase data to include extra nonce values and strings identifying the mining pool, as we will see in the following sections.