From 98d9ebd1fd5538bcf7e6c5c22042d76fc1484fe7 Mon Sep 17 00:00:00 2001 From: clenser Date: Wed, 18 Oct 2023 15:50:41 +0000 Subject: [PATCH] Edited ch05_wallets.adoc with Atlas code editor --- ch05_wallets.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/ch05_wallets.adoc b/ch05_wallets.adoc index cf6fac15..c30fee5a 100644 --- a/ch05_wallets.adoc +++ b/ch05_wallets.adoc @@ -211,10 +211,10 @@ We'll provide a detailed exploration of HD wallets in <>. ==== Seeds and Recovery Codes -HD wallets are a very powerful mechanism for managing many +HD wallets((("wallets", "recovery codes", id="wallet-recovery2")))((("recovery codes", id="recovery-code2"))) are a very powerful mechanism for managing many keys all derived from a single seed. If your wallet database is ever corrupted or lost, you can regenerate all of the private keys -for your wallet using your original seed. But, if someone else gets +for your wallet using your ((("seeds")))original seed. But, if someone else gets your seed, they can also generate all of the private keys, allowing them to steal all of the bitcoins from a single-sig wallet and reduce the security of bitcoins in multisignature wallets. In this section, we'll @@ -403,7 +403,7 @@ Many users and developers disagree on which approach is better, with some strongly in favor of plausible deniability and others preferring the increased safety that error detection gives novice users and those under duress. We suspect the debate will continue for as long as recovery -codes continue to be widely used. +codes continue to be widely ((("wallets", "recovery codes", startref="wallet-recovery2")))((("recovery codes", startref="recovery-code2")))used. **** ==== Backing Up Nonkey Data