From bf2c21a22dfe3706d3ad02b2c5be178c802b47a7 Mon Sep 17 00:00:00 2001 From: "myarbrough@oreilly.com" Date: Tue, 25 Nov 2014 12:55:25 -0800 Subject: [PATCH] Made changes to ch05.asciidoc --- ch05.asciidoc | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/ch05.asciidoc b/ch05.asciidoc index 03b8d3a8..7cc33cc1 100644 --- a/ch05.asciidoc +++ b/ch05.asciidoc @@ -44,9 +44,7 @@ The bitcoin network is designed to propagate transactions and blocks to all node [[tx_structure]] === Transaction Structure -((("transactions","structure of")))A transaction is a((("data structure"))) _data structure_ that encodes a transfer of value from a source of funds, called an((("inputs, defined"))) _input_, to a destination, called an((("outputs, defined"))) _output_. Transaction inputs and outputs are not related to accounts or identities. Instead, you should think of them as bitcoin amounts—chunks of bitcoin—being locked with a specific secret that only the owner, or person who knows the secret, can unlock. - -A transaction contains a number of fields, as shown in <>. +((("transactions","structure of")))A transaction is a((("data structure"))) _data structure_ that encodes a transfer of value from a source of funds, called an((("inputs, defined"))) _input_, to a destination, called an((("outputs, defined"))) _output_. Transaction inputs and outputs are not related to accounts or identities. Instead, you should think of them as bitcoin amounts—chunks of bitcoin—being locked with a specific secret that only the owner, or person who knows the secret, can unlock. A transaction contains a number of fields, as shown in <>. [[tx_data_structure]] .The structure of a transaction