mirror of
https://github.com/bitcoinbook/bitcoinbook
synced 2025-04-22 18:19:11 +00:00
Edited ch05_wallets.adoc with Atlas code editor
This commit is contained in:
parent
fde40b87e2
commit
de2d20901d
@ -20,7 +20,7 @@ In those cases, we'll describe the various options available.
|
||||
|
||||
=== Independent Key Generation
|
||||
|
||||
Wallets ((("wallets", "key generation", "independent", id="wallet-keygen-independent")))((("key generation", "independent", id="keygen-independent")))((("independent key generation", id="independent-keygen")))for physical cash hold that cash,
|
||||
Wallets ((("wallets", "key generation", "independent", id="wallet-keygen-independent")))((("key generation", "independent", id="keygen-independent")))((("independent key generation", id="independent-keygen")))((("public key cryptography", "wallet recovery key generation", see="key generation")))for physical cash hold that cash,
|
||||
so it's unsurprising that many people mistakenly believe that
|
||||
Bitcoin wallets contain bitcoins. In fact, what many people call a
|
||||
Bitcoin wallet--which we call a _wallet database_ to distinguish it
|
||||
@ -65,7 +65,7 @@ algorithm.
|
||||
|
||||
==== Deterministic Key Generation
|
||||
|
||||
A hash function will always produce the same output when given the same
|
||||
A hash function((("wallets", "key generation", "deterministic", id="wallet-keygen-determine")))((("key generation", "deterministic", id="keygen-determine")))((("deterministic key generation", id="determine-keygen")))((("hash functions", "deterministic key generation", id="hash-determine"))) will always produce the same output when given the same
|
||||
input, but if the input is changed even slightly, the output will be
|
||||
different. If the function is cryptographically secure, nobody should
|
||||
be able to predict the new output--not even if they know the new input.
|
||||
@ -108,7 +108,7 @@ A logical diagram of basic sequential deterministic key generation is
|
||||
shown in <<Type1_wallet>>. However, modern wallet applications have a
|
||||
more clever way of accomplishing this that allows public keys to be
|
||||
derived separately from their corresponding private keys, making it
|
||||
possible to store private keys more securely than public keys.
|
||||
possible to store private keys more securely than ((("wallets", "key generation", "deterministic", startref="wallet-keygen-determine")))((("key generation", "deterministic", startref="keygen-determine")))((("deterministic key generation", startref="determine-keygen")))((("hash functions", "deterministic key generation", startref="hash-determine")))public keys.
|
||||
|
||||
[[Type1_wallet]]
|
||||
[role="smallersixty"]
|
||||
|
Loading…
Reference in New Issue
Block a user