From 8d19b6da5b7c3cdc430f4575b0bdb2fed925cf52 Mon Sep 17 00:00:00 2001 From: Shannon Appelcline Date: Tue, 11 Aug 2020 13:10:19 -1000 Subject: [PATCH] Update 16_3_Using_BIP32_in_Libwally.md --- 16_3_Using_BIP32_in_Libwally.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/16_3_Using_BIP32_in_Libwally.md b/16_3_Using_BIP32_in_Libwally.md index e4029c3..85aaeff 100644 --- a/16_3_Using_BIP32_in_Libwally.md +++ b/16_3_Using_BIP32_in_Libwally.md @@ -131,6 +131,8 @@ An HD wallet allows you to generate a vast number of keys from a single seeds. Y > :fire: ***What is the power of BIP32?*** Keys are the most difficult (and most dangerous) element of most cryptographic operations. If you lose them, you lose whatever the key protected. BIP32 ensures that you just need to know one key, the seed, rather than a huge number of different keys for different addresses. +> :fire: ***What is the power of BIP32 in Libwally?*** Bitcoind already does address creation for you, which means you don't usually have to worry about deriving addresses in this way. However, using the BIP32 functions of Libwally can be very useful if you have an offline machine where you need to derive addresses, possibly based on a seed passed out of `bitcoind` to your offline device. + ## What's Next? Learn more about "Programming Bitcoin with Libwally" in [16.4: Using PSBTs in Libwally](16_4_Using_PSBTs_in_Libwally.md).