mirror of
https://github.com/bitcoinbook/bitcoinbook
synced 2024-11-21 23:58:09 +00:00
index edits 3
This commit is contained in:
parent
c8d9508cdd
commit
84c455849e
@ -235,7 +235,7 @@ created, this unit didn't have a name and some developers simply called
|
||||
it the _base unit._ Later many users began calling this unit a
|
||||
_satoshi_ (sat) in honor of Bitcoin's creator. In <<transaction-chain>>
|
||||
and some other illustrations in this book, we use satoshi values because
|
||||
that's what the protocol itself ((("satoshis")))((("transaction chains", startref="transaction-chains")))uses.
|
||||
that's what the protocol itself ((("satoshis")))uses.
|
||||
====
|
||||
|
||||
==== Making Change
|
||||
@ -270,7 +270,7 @@ Changeless transactions are only a practical option if the amount being
|
||||
spent is roughly the same as the amount available in the transaction
|
||||
inputs minus the anticipated transaction fee. In <<transaction-chain>>,
|
||||
we see Bob creating Tx3 as a changeless transaction that spends the
|
||||
output he ((("transactions", "change output", startref="transaction-change-output")))((("change output", startref="change-output")))((("outputs", "change output", startref="output-change")))received in Tx2.
|
||||
output he received in Tx2.
|
||||
|
||||
==== Coin Selection
|
||||
|
||||
|
@ -1014,7 +1014,7 @@ Bitcoin miners about 32 billion years.
|
||||
|
||||
Although we do not believe there is any immediate threat to anyone
|
||||
creating new P2SH addresses, we recommend all new wallets use newer
|
||||
types of addresses to eliminate address collision attacks((("public key cryptography", "hash functions and", startref="pub-key-hash2")))((("hash functions", "Bitcoin payments and", startref="hash-payment2")))((("payments", "with hash functions", secondary-sortas="hash functions", startref="payment-hash2")))((("P2SH (pay to script hash)", startref="p2sh-ch4")))((("collision attacks", startref="collision")))((("addresses", "P2SH (pay to script hash)", startref="address-p2sh-ch4"))) as a concern.
|
||||
types of addresses to eliminate address collision attacks((("public key cryptography", "hash functions and", startref="pub-key-hash2")))((("hash functions", "Bitcoin payments and", startref="hash-payment2")))((("payments", "with hash functions", secondary-sortas="hash functions", startref="payment-hash2")))((("P2SH (pay to script hash)", startref="p2sh-ch4")))((("addresses", "P2SH (pay to script hash)", startref="address-p2sh-ch4"))) as a concern.
|
||||
****
|
||||
|
||||
=== Bech32 Addresses
|
||||
|
Loading…
Reference in New Issue
Block a user