From b80466aac20f48ae0907f9464d622373c93748b9 Mon Sep 17 00:00:00 2001 From: nadams Date: Thu, 18 May 2017 12:30:22 -0700 Subject: [PATCH] Edited ch02.asciidoc with Atlas code editor --- ch02.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ch02.asciidoc b/ch02.asciidoc index b2814777..f2411d2f 100644 --- a/ch02.asciidoc +++ b/ch02.asciidoc @@ -279,7 +279,7 @@ image::images/mbc2_0209.png["Alice's transaction included in a block"] Bob can now spend the output from this and other transactions. For example, Bob can pay a contractor or supplier by transferring value from Alice's coffee cup payment to these new owners. Most likely, Bob's bitcoin software will aggregate many small payments into a larger payment, perhaps concentrating all the day's bitcoin revenue into a single transaction. This would aggregate the various payments into a single output (and a single address). For a diagram of an aggregating transaction, see <>. -As Bob spends the payments received from Alice and other customers, he extends the chain of transactions. Let's assume that Bob pays his web designer Gopesh in Bangalore for a new website page. Now the chain of transactions will look like <>. +As Bob spends the payments received from Alice and other customers, he extends the chain of transactions. Let's assume that Bob pays his web designer Gopesh((("use cases", "offshore contract services"))) in Bangalore for a new website page. Now the chain of transactions will look like <>. [[block-alice2]] .Alice's transaction as part of a transaction chain from Joe to Gopesh