From 6588080911bef4968bd4d2cb6aa3e2500e6ed0a2 Mon Sep 17 00:00:00 2001 From: clenser Date: Tue, 17 Oct 2023 00:24:30 +0000 Subject: [PATCH] Edited ch04_keys.adoc with Atlas code editor --- ch04_keys.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ch04_keys.adoc b/ch04_keys.adoc index d81fdf63..65ad7034 100644 --- a/ch04_keys.adoc +++ b/ch04_keys.adoc @@ -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]]