From a399132212606488c1059805348455a9611285f1 Mon Sep 17 00:00:00 2001 From: "myarbrough@oreilly.com" Date: Tue, 18 Nov 2014 07:59:24 -0800 Subject: [PATCH] Made changes to ch05.asciidoc --- ch05.asciidoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/ch05.asciidoc b/ch05.asciidoc index d6bf6c26..76e71232 100644 --- a/ch05.asciidoc +++ b/ch05.asciidoc @@ -351,7 +351,7 @@ The five standard types of transaction scripts are pay-to-public-key hash (P2PKH [[p2pkh]] ==== Pay-to-Public-Key Hash (P2PKH) -((("pay-to-public-key hash (P2PKH)", id="ix_ch05-asciidoc15", range="startofrange")))((("transactions","pay-to-public-key hash", id="ix_ch05-asciidoc16", range="startofrange")))The vast majority of transactions processed on the bitcoin network are pay-to-public-key hash, also known as P2PKH transactions. These contain a locking script that encumbers the output with a public key hash, more commonly known as a bitcoin address. Transactions that pay a bitcoin address contain P2PKH scripts. An output locked by a P2PKH script can be unlocked (spent) by presenting a public key and a digital signature created by the corresponding private key. +((("pay-to-public-key hash (P2PKH)", id="ix_ch05-asciidoc15", range="startofrange")))((("transactions","pay-to-public-key hash", id="ix_ch05-asciidoc16", range="startofrange")))The vast majority of transactions processed on the bitcoin network are P2PKH transactions. These contain a locking script that encumbers the output with a public key hash, more commonly known as a bitcoin address. Transactions that pay a bitcoin address contain P2PKH scripts. An output locked by a P2PKH script can be unlocked (spent) by presenting a public key and a digital signature created by the corresponding private key. For example, let's look at Alice's payment to Bob's Cafe again. Alice made a payment of 0.015 bitcoin to the cafe's bitcoin address. That transaction output would have a locking script of the form: @@ -379,11 +379,11 @@ When executed, this combined script will evaluate to TRUE if, and only if, the u <> and <> show (in two parts) a step-by-step execution of the combined script, which will prove this is a valid transaction.(((range="endofrange", startref="ix_ch05-asciidoc16")))(((range="endofrange", startref="ix_ch05-asciidoc15"))) [[P2PubKHash1]] -.Evaluating a script for a Pay-to-Public-Key-Hash transaction (Part 1 of 2) +.Evaluating a script for a P2PKH transaction (Part 1 of 2) image::images/msbt_0503.png["Tx_Script_P2PubKeyHash_1"] [[P2PubKHash2]] -.Evaluating a script for a Pay-to-Public-Key-Hash transaction (Part 2 of 2) +.Evaluating a script for a P2PKH transaction (Part 2 of 2) image::images/msbt_0504.png["Tx_Script_P2PubKeyHash_2"] [[p2pk]]