From 6a3b82facd516f7e732e619a687158a719fadf5d Mon Sep 17 00:00:00 2001 From: clenser Date: Wed, 18 Oct 2023 16:10:06 +0000 Subject: [PATCH] Edited ch05_wallets.adoc with Atlas code editor --- ch05_wallets.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ch05_wallets.adoc b/ch05_wallets.adoc index 77c43fdf..6a5714ac 100644 --- a/ch05_wallets.adoc +++ b/ch05_wallets.adoc @@ -506,7 +506,7 @@ and additional ((("wallets", "nonkey data", "backing up", startref="wallet-nonke ==== Backing Up Key Derivation Paths -In a BIP32 tree of keys, there are approximately four billion first-level +In a ((("wallets", "key generation", "backing up derivation paths", id="wallet-keygen-backups")))((("key generation", "backing up derivation paths", id="keygen-backups")))((("backing up", "key derivation paths", id="backup-key-derive")))BIP32 tree of keys, there are approximately four billion first-level keys and each of those keys can have its own four billion children, with those children each potentially having four billion children of their own, and so on. It's not possible for a wallet application to generate @@ -652,7 +652,7 @@ single signature scripts to use implicit paths. Wallet applications designed for multiple signatures or other advanced scripts are increasingly adopting support for explicit paths using descriptors. Applications that do both will usually conform to the standards for -implicit paths and also provide descriptors. +implicit paths and also provide ((("wallets", "key generation", "backing up derivation paths", startref="wallet-keygen-backups")))((("key generation", "backing up derivation paths", startref="keygen-backups")))((("backing up", "key derivation paths", startref="backup-key-derive")))descriptors. === A Wallet Technology Stack in Detail