aboutsummaryrefslogtreecommitdiff
path: root/doc/release-notes.md
diff options
context:
space:
mode:
authorJohn Newbery <john@johnnewbery.com>2018-01-11 16:55:06 -0500
committerJohn Newbery <john@johnnewbery.com>2018-01-15 10:26:15 -0500
commit97c3cada9266e0aebd0f97c5e9de09a7d10456fa (patch)
treea2e7fdff56ec008fe27578e56740e78b3f5be86c /doc/release-notes.md
parent0910cbe4ef31eb95fd76c7c2f820419fe64a3150 (diff)
downloadbitcoin-97c3cada9266e0aebd0f97c5e9de09a7d10456fa.tar.xz
[docs] Clarify -walletdir usage
Diffstat (limited to 'doc/release-notes.md')
-rw-r--r--doc/release-notes.md34
1 files changed, 21 insertions, 13 deletions
diff --git a/doc/release-notes.md b/doc/release-notes.md
index d92666da72..fb8e0f7f59 100644
--- a/doc/release-notes.md
+++ b/doc/release-notes.md
@@ -75,19 +75,27 @@ There is a checkbox to mark the transaction as final.
The RPC default remains unchanged: to use RBF, launch with `-walletrbf=1` or
use the `replaceable` argument for individual transactions.
-Custom wallet directories
----------------------
-The ability to specify a directory other than the default data directory in which to store
-wallets has been added. An existing directory can be specified using the `-walletdir=<dir>`
-argument. Wallets loaded via `-wallet` arguments must be in this wallet directory. Care should be taken
-when choosing a wallet directory location, as if it becomes unavailable during operation,
-funds may be lost.
-
-Default wallet directory change
---------------------------
-On new installations (if the data directory doesn't exist), wallets will now be stored in a
-new `wallets/` subdirectory inside the data directory. If this `wallets/` subdirectory
-doesn't exist (i.e. on existing nodes), the current datadir root is used instead, as it was.
+Wallets directory configuration (`-walletdir`)
+----------------------------------------------
+
+Bitcoin Core now has more flexibility in where the wallets directory can be
+located. Previously wallet database files were stored at the top level of the
+bitcoin data directory. The behavior is now:
+
+- For new installations (where the data directory doesn't already exist),
+ wallets will now be stored in a new `wallets/` subdirectory inside the data
+ directory by default.
+- For existing nodes (where the data directory already exists), wallets will be
+ stored in the data directory root by default. If a `wallets/` subdirectory
+ already exists in the data directory root, then wallets will be stored in the
+ `wallets/` subdirectory by default.
+- The location of the wallets directory can be overridden by specifying a
+ `-walletdir=<path>` option where `<path>` can be an absolute path or a
+ relative path (relative to the current working directory). `<path>` can
+ also be a path to symlink to a directory.
+
+Care should be taken when choosing the wallets directory location, as if it
+becomes unavailable during operation, funds may be lost.
Low-level RPC changes
----------------------