From 738e124b0a655dc26ed84d959fd722c84b183531 Mon Sep 17 00:00:00 2001 From: clenser Date: Tue, 17 Oct 2023 17:53:20 +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 70e45b78..39eb3bcd 100644 --- a/ch04_keys.adoc +++ b/ch04_keys.adoc @@ -1107,7 +1107,7 @@ image::images/mbc3_0409.png["The same bech32 address QR encoded in lowercase and ==== Problems with Bech32 Addresses -Bech32 addresses would have been a success in every area except for one +Bech32 addresses((("public key cryptography", "bech32 addresses", "problems with", id="pub-key-bech32-prob")))((("bech32 addresses", "problems with", id="bech32-prob"))) would have been a success in every area except for one problem. The mathematical guarantees about their ability to detect errors only apply if the length of the address you enter into a wallet is the same length of the original address. If you add or remove any @@ -1155,7 +1155,7 @@ or 62 characters long, so someone would need to add or remove the letter "q" from the penultimate position of a bech32 address 20 times in order to send money to an invalid address without a wallet being able to detect it. However, it would become a problem for users in the future if -a segwit-based upgrade were ever to be implemented. +a segwit-based upgrade were ever to be ((("public key cryptography", "bech32 addresses", "problems with", startref="pub-key-bech32-prob")))((("bech32 addresses", "problems with", startref="bech32-prob")))implemented. ==== Bech32m