From b6764791333ac4ffd4d82daf3bf67c6c7e1828e8 Mon Sep 17 00:00:00 2001 From: clenser Date: Wed, 18 Oct 2023 16:25:00 +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 4ee331bd..f345694d 100644 --- a/ch05_wallets.adoc +++ b/ch05_wallets.adoc @@ -789,7 +789,7 @@ data and the length of recovery code in((("wallets", "recovery codes", "generati [[recovery_to_seed]] ===== From recovery code to seed -The recovery code +The ((("wallets", "recovery codes", "seed generation", id="wallet-recovery-bip39-seed")))((("recovery codes", "seed generation", id="recovery-code-bip39-seed")))((("BIP39 recovery codes", "seed generation", id="bip39-recovery-seed")))((("entropy", "seed generation", id="entropy-seed-generate")))((("seeds", "generating", id="seed-generate")))((("key-stretching functions", id="key-stretch")))recovery code represents entropy with a length of 128 to 256 bits. The entropy is then used to derive a longer (512-bit) seed through the use of the key-stretching function PBKDF2. The seed produced is then used to build @@ -844,7 +844,7 @@ designed for compatibility with hardware signing devices with low-powered CPUs. Some alternatives to BIP39 use stronger key-stretching parameters, such as Aezeed's 32,768 rounds of hashing using the more complex Scrypt algorithm, although they may not be as convenient to run -on hardware signing devices. +on hardware signing((("wallets", "recovery codes", "seed generation", startref="wallet-recovery-bip39-seed")))((("recovery codes", "seed generation", startref="recovery-code-bip39-seed")))((("BIP39 recovery codes", "seed generation", startref="bip39-recovery-seed")))((("entropy", "seed generation", startref="entropy-seed-generate")))((("seeds", "generating", startref="seed-generate")))((("key-stretching functions", startref="key-stretch"))) devices. ==== Tables pass:[