mirror of
https://github.com/bitcoinbook/bitcoinbook
synced 2024-11-13 19:38:56 +00:00
Edited ch04_keys.adoc with Atlas code editor
This commit is contained in:
parent
45898988b9
commit
6588080911
@ -749,7 +749,7 @@ image::images/mbc3_0407.png["pubkey_to_address"]
|
||||
//https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2011-November/000778.html
|
||||
|
||||
|
||||
When Bitcoin was first authored, its developers only knew how to create
|
||||
When ((("public key cryptography", "compressed public keys", id="pub-key-compress")))((("compressed public keys", id="compress-pub-key")))((("uncompressed public keys", id="uncompress-pub-key")))Bitcoin was first authored, its developers only knew how to create
|
||||
65-byte public keys. However, a later developer became aware of an
|
||||
alternative encoding for public keys that used only 33 bytes and which
|
||||
was backward compatible with all Bitcoin full nodes at the time,
|
||||
@ -847,7 +847,7 @@ to scan for the correct type can lead to the user not being able to
|
||||
spend their full balance. To resolve this issue, when private keys are
|
||||
exported from a wallet, the WIF that is used to
|
||||
represent them is implemented slightly differently in newer Bitcoin
|
||||
wallets, to indicate that these private keys have been used to produce
|
||||
wallets, to indicate that these private keys have been used to produce((("public key cryptography", "compressed public keys", startref="pub-key-compress")))((("compressed public keys", startref="compress-pub-key")))((("uncompressed public keys", startref="uncompress-pub-key")))
|
||||
compressed public keys.
|
||||
|
||||
[[addresses_for_p2sh]]
|
||||
|
Loading…
Reference in New Issue
Block a user