aboutsummaryrefslogtreecommitdiff
path: root/doc/release-notes.md
diff options
context:
space:
mode:
authorWladimir J. van der Laan <laanwj@gmail.com>2018-01-18 21:08:48 +0100
committerWladimir J. van der Laan <laanwj@gmail.com>2018-01-18 21:09:27 +0100
commite839d6570d9d0575a63ac45d35ad8bc248aeaacc (patch)
tree20c55a96a5a9b91f22d87009d9e4804b0ccada75 /doc/release-notes.md
parent10d10d7fadcf5f937c8e782224c5f2b34462856b (diff)
parent97c3cada9266e0aebd0f97c5e9de09a7d10456fa (diff)
Merge #12166: [docs] Clarify -walletdir usage
97c3cad [docs] Clarify -walletdir usage (John Newbery) Pull request description: After discussion with @ryanofsky around #11687 , I think this documentation is a bit clearer for how the new `-walletdir` argument works. Tree-SHA512: f279cab82524dbc0d75e6f9891f0e228ec4c8d0df3e16f351057fa243ddd263ff786f05383fd00a09b89edcc07dab211be5b64387f77271edf8af0177bcf667d
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 bf4a725574..ecca08d96d 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
----------------------