From f75af6a09c0460c51d7a94607c70cac242a34759 Mon Sep 17 00:00:00 2001 From: clenser Date: Tue, 17 Oct 2023 17:58:57 +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 3b0e3082..a2efa80c 100644 --- a/ch04_keys.adoc +++ b/ch04_keys.adoc @@ -1181,7 +1181,7 @@ types contain an internal version byte that makes determining that easy. ===== Encoding and Decoding bech32m addresses -In this section, we'll look at the encoding and parsing rules for +In this((("encoding", "bech32m addresses", id="encode-bech32m")))((("decoding", "bech32m addresses", id="decode-bech32m"))) section, we'll look at the encoding and parsing rules for bech32m Bitcoin addresses since they encompass the ability to parse bech32 addresses and are the current recommended address format for Bitcoin wallets. @@ -1418,7 +1418,7 @@ recommend that you use the test vectors provided in BIP350. We also ask that you ensure your code passes the test vectors related to paying future segwit versions that haven't been defined yet. This will help make your software usable for many years to come even if you aren't able to add -support for new Bitcoin features as soon as they become ((("public key cryptography", "bech32 addresses", "bech32m", startref="pub-key-bech32-bech32m")))((("bech32 addresses", "bech32m", startref="bech32-bech32m")))((("bech32m addresses", startref="bech32m")))available. +support for new Bitcoin features as soon as they become ((("public key cryptography", "bech32 addresses", "bech32m", startref="pub-key-bech32-bech32m")))((("bech32 addresses", "bech32m", startref="bech32-bech32m")))((("bech32m addresses", startref="bech32m")))((("encoding", "bech32m addresses", startref="encode-bech32m")))((("decoding", "bech32m addresses", startref="decode-bech32m")))available. [[priv_formats]] ==== Private Key Formats