From 844571bc1ed2712fad022bc2864afd4156ef2a64 Mon Sep 17 00:00:00 2001 From: clenser Date: Wed, 18 Oct 2023 15:54:17 +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 b6ec3b6a..553be9f8 100644 --- a/ch05_wallets.adoc +++ b/ch05_wallets.adoc @@ -348,7 +348,7 @@ status]. .Recovery Code Passphrases **** -The BIP39, Electrum v2, Aezeed, and SLIP39 schemes may all be used with an +The BIP39, ((("passphrases (for recovery codes)", id="passphrase")))Electrum v2, Aezeed, and SLIP39 schemes may all be used with an optional passphrase. If the only place you keep this passphrase is in your memory, it has the same advantages and disadvantages as memorizing your recovery code. However, there's a further set of trade-offs @@ -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 ((("wallets", "recovery codes", startref="wallet-recovery2")))((("recovery codes", startref="recovery-code2")))used. +codes continue to be widely ((("wallets", "recovery codes", startref="wallet-recovery2")))((("recovery codes", startref="recovery-code2")))((("passphrases (for recovery codes)", startref="passphrase")))used. **** ==== Backing Up Nonkey Data