From 3122090cce25ccc7dadc6e5208a9fb0838236290 Mon Sep 17 00:00:00 2001 From: "Minh T. Nguyen" Date: Fri, 6 Jun 2014 07:56:13 -0700 Subject: [PATCH] Correcting the block number of Alice's transaction as reported by Issue #40 --- ch02.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ch02.asciidoc b/ch02.asciidoc index 2d92a983..0ebd2a27 100644 --- a/ch02.asciidoc +++ b/ch02.asciidoc @@ -236,7 +236,7 @@ A few minutes later, a new block, #277317 is mined by another miner. As this new In the diagram below we can see block #277316, which contains Alice's transaction. Below it are 277,315 blocks, linked to each other in a chain of blocks (blockchain) all the way back to block #0, the genesis block. Over time, as the "height" in blocks increases, so does the computation difficulty for each block and the chain as a whole. The blocks mined after the one that contains Alice's transaction act as further assurance, as they pile on more computation in a longer and longer chain. The blocks above count as "confirmations". By convention, any block with more than 6 confirmations is considered irrevocable, as it would require an immense amount of computation to invalidate and re-calculate six blocks. We will examine the process of mining and the way it builds trust in more detail in <>. [[block-alice]] -.Alice's transaction included in block #277,317 +.Alice's transaction included in block #277,316 image::images/Blockchain_height_and_depth.png["Alice's transaction included in a block"] === Spending the transaction