aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorJonas Schnelli <dev@jonasschnelli.ch>2016-07-21 21:19:02 +0200
committerJonas Schnelli <dev@jonasschnelli.ch>2016-07-27 15:56:57 +0200
commitf142c11ac634df487cc4bc65a5f1c9a3e3563dd9 (patch)
tree40561d6272632e4b8ff22583c48cfe5b2bece953 /doc
parent18b8ee1cd1b2c95faac53e49b9023200679f2bb1 (diff)
downloadbitcoin-f142c11ac634df487cc4bc65a5f1c9a3e3563dd9.tar.xz
[0.13] Create a new HD seed after encrypting the wallet
Diffstat (limited to 'doc')
-rw-r--r--doc/release-notes.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/release-notes.md b/doc/release-notes.md
index bb9118762b..ad11fafd32 100644
--- a/doc/release-notes.md
+++ b/doc/release-notes.md
@@ -135,6 +135,8 @@ Existing wallets will still use traditional key generation.
Backups of HD wallets, regardless of when they have been created, can
therefore be used to re-generate all possible private keys, even the
ones which haven't already been generated during the time of the backup.
+**Attention:** Encrypting the wallet will create a new seed which requires
+a new backup!
HD key generation for new wallets can be disabled by `-usehd=0`. Keep in
mind that this flag only has affect on newly created wallets.