mirror of
https://github.com/bitcoinbook/bitcoinbook
synced 2024-11-21 23:58:09 +00:00
renumbering images
This commit is contained in:
parent
a2b3ef21ad
commit
e59fa0c1fa
@ -84,7 +84,7 @@ TODO: Replace QR code with test-BTC address
|
||||
|
||||
[[invoice-QR]]
|
||||
.Invoice QR code
|
||||
image::images/mbc3_0202.png["payment-request"]
|
||||
image::images/mbc3_0201.png["payment-request"]
|
||||
|
||||
Unlike a QR code that simply contains a destination Bitcoin address, this
|
||||
invoice is a QR-encoded URI that contains a destination address,
|
||||
@ -172,7 +172,7 @@ transaction over to a new owner identified by a Bitcoin ((("transactions", "inpu
|
||||
|
||||
[[transaction-double-entry]]
|
||||
.Transaction as double-entry bookkeeping
|
||||
image::images/mbc3_0203.png["Transaction Double-Entry"]
|
||||
image::images/mbc3_0202.png["Transaction Double-Entry"]
|
||||
|
||||
==== Transaction Chains
|
||||
|
||||
@ -218,7 +218,7 @@ change.
|
||||
|
||||
[[transaction-chain]]
|
||||
.A chain of transactions, where the output of one transaction is the input of the next transaction
|
||||
image::images/mbc3_0204.png["Transaction chain"]
|
||||
image::images/mbc3_0203.png["Transaction chain"]
|
||||
|
||||
[TIP]
|
||||
====
|
||||
@ -290,7 +290,7 @@ transaction has one input and two outputs and is shown in
|
||||
|
||||
[[transaction-common]]
|
||||
.Most common transaction
|
||||
image::images/mbc3_0205.png["Common Transaction"]
|
||||
image::images/mbc3_0204.png["Common Transaction"]
|
||||
|
||||
Another common form of transaction ((("consolidation transactions")))is a _consolidation transaction_, which spends several inputs
|
||||
into a single output (<<transaction-consolidating>>). This represents
|
||||
@ -300,7 +300,7 @@ generated by wallets and businesses to clean up lots of smaller amounts.
|
||||
|
||||
[[transaction-consolidating]]
|
||||
.Consolidation transaction aggregating funds
|
||||
image::images/mbc3_0206.png["Aggregating Transaction"]
|
||||
image::images/mbc3_0205.png["Aggregating Transaction"]
|
||||
|
||||
Finally, another transaction form that is seen often on the
|
||||
blockchain ((("payment batching")))is _payment batching_, which pays to multiple outputs
|
||||
@ -311,7 +311,7 @@ employees.
|
||||
|
||||
[[transaction-distributing]]
|
||||
.Batch transaction distributing funds
|
||||
image::images/mbc3_0207.png["Distributing Transaction"]
|
||||
image::images/mbc3_0206.png["Distributing Transaction"]
|
||||
|
||||
=== Constructing a Transaction
|
||||
|
||||
@ -583,7 +583,7 @@ the process of mining and the way it builds confidence in more ((("bitcoins", "m
|
||||
|
||||
[[block-alice1]]
|
||||
.Alice's transaction included in a block
|
||||
image::images/mbc3_0208.png["Alice's transaction included in a block"]
|
||||
image::images/mbc3_0207.png["Alice's transaction included in a block"]
|
||||
|
||||
=== Spending the Transaction
|
||||
|
||||
@ -611,7 +611,7 @@ look like <<block-alice2>>.
|
||||
|
||||
[[block-alice2]]
|
||||
.Alice's transaction as part of a transaction chain from Joe to Gopesh
|
||||
image::images/mbc3_0209.png["Alice's transaction as part of a transaction chain"]
|
||||
image::images/mbc3_0208.png["Alice's transaction as part of a transaction chain"]
|
||||
|
||||
In this chapter, we((("transactions", "spending bitcoins", startref="transaction-spend2")))((("bitcoins", "spending", startref="bitcoin-spend2")))((("spending bitcoins", startref="spend-bitcoin2"))) saw how transactions build a chain that moves value
|
||||
from owner to owner. We also tracked Alice's transaction from the
|
||||
|
@ -1347,7 +1347,7 @@ parent public key, as shown in the diagram in <<CKDprime>>.
|
||||
|
||||
[[CKDprime]]
|
||||
.Hardened derivation of a child key; omits the parent public key
|
||||
image::images/mbc3_0510.png["ChildHardPrivateDerivation"]
|
||||
image::images/mbc3_0509.png["ChildHardPrivateDerivation"]
|
||||
|
||||
|
||||
When the hardened private derivation function is used, the resulting
|
||||
|
Loading…
Reference in New Issue
Block a user