From 11be2850c48f6cb546d4322cf50b7ba961d7cd3d Mon Sep 17 00:00:00 2001 From: "judymcconville@roadrunner.com" Date: Mon, 1 May 2017 15:10:55 -0700 Subject: [PATCH] Edited ch09.asciidoc with Atlas code editor --- ch09.asciidoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ch09.asciidoc b/ch09.asciidoc index d110d6ed..1ffeaea9 100644 --- a/ch09.asciidoc +++ b/ch09.asciidoc @@ -67,7 +67,7 @@ A block's _block hash_ always identifies a single block uniquely. A block also a === The Genesis Block -The first block in the blockchain is called the genesis block and was created in 2009. It is the common ancestor of all the blocks in the blockchain, meaning that if you start at any block and follow the chain backward in time, you will eventually arrive at the genesis block. +((("blocks", "genesis block")))((("blockchain technology", "genesis block")))The first block in the blockchain is called the genesis block and was created in 2009. It is the common ancestor of all the blocks in the blockchain, meaning that if you start at any block and follow the chain backward in time, you will eventually arrive at the genesis block. Every node always starts with a blockchain of at least one block because the genesis block is statically encoded within the bitcoin client software, such that it cannot be altered. Every node always "knows" the genesis block's hash and structure, the fixed time it was created, and even the single transaction within. Thus, every node has the starting point for the blockchain, a secure "root" from which to build a trusted blockchain. @@ -115,7 +115,7 @@ The genesis block contains a hidden message within it. The coinbase transaction === Linking Blocks in the Blockchain -Bitcoin full nodes maintain a local copy of the blockchain, starting at the genesis block. The local copy of the blockchain is constantly updated as new blocks are found and used to extend the chain. As a node receives incoming blocks from the network, it will validate these blocks and then link them to the existing blockchain. To establish a link, a node will examine the incoming block header and look for the "previous block hash." +((("blocks", "linking blocks in the blockchaing")))((("blockchain technology", "linking blocks in the blockchaing")))Bitcoin full nodes maintain a local copy of the blockchain, starting at the genesis block. The local copy of the blockchain is constantly updated as new blocks are found and used to extend the chain. As a node receives incoming blocks from the network, it will validate these blocks and then link them to the existing blockchain. To establish a link, a node will examine the incoming block header and look for the "previous block hash." Let's assume, for example, that a node has 277,314 blocks in the local copy of the blockchain. The last block the node knows about is block 277,314, with a block header hash of: