Changeset View
Changeset View
Standalone View
Standalone View
doc/release-notes.md
Bitcoin ABC version 0.19.7 is now available from: | Bitcoin ABC version 0.19.7 is now available from: | ||||
<https://download.bitcoinabc.org/0.19.7/> | <https://download.bitcoinabc.org/0.19.7/> | ||||
This release includes the following features and fixes: | This release includes the following features and fixes: | ||||
- `-includeconf=<file>` can be used to include additional configuration files. | - `-includeconf=<file>` can be used to include additional configuration files. | ||||
Only works inside the `bitcoin.conf` file, not inside included files or from | Only works inside the `bitcoin.conf` file, not inside included files or from | ||||
command-line. Multiple files may be included. Can be disabled from command- | command-line. Multiple files may be included. Can be disabled from command- | ||||
line via `-noincludeconf`. Note that multi-argument commands like | line via `-noincludeconf`. Note that multi-argument commands like | ||||
`-includeconf` will override preceding `-noincludeconf`, i.e. | `-includeconf` will override preceding `-noincludeconf`, i.e. | ||||
noincludeconf=1 | noincludeconf=1 | ||||
includeconf=relative.conf | includeconf=relative.conf | ||||
as bitcoin.conf will still include `relative.conf`. | as bitcoin.conf will still include `relative.conf`. | ||||
- The `createrawtransaction` RPC will now accept an array or dictionary (kept for compatibility) for the `outputs` parameter. This means the order of transaction outputs can be specified by the client. | - The `createrawtransaction` RPC will now accept an array or dictionary (kept for compatibility) for the `outputs` parameter. This means the order of transaction outputs can be specified by the client. | ||||
- The new RPC `testmempoolaccept` can be used to test acceptance of a transaction to the mempool without adding it. | - The new RPC `testmempoolaccept` can be used to test acceptance of a transaction to the mempool without adding it. | ||||
- The `-wallet=<path>` option now accepts full paths instead of requiring | - The `-wallet=<path>` option now accepts full paths instead of requiring | ||||
wallets to be located in the -walletdir directory. When wallets are located | wallets to be located in the -walletdir directory. | ||||
in different directories, wallet data will be stored independently, so data | |||||
from every wallet is not mixed into the same | If `-wallet=<path>` is specified with a path that does not exist, it will now | ||||
<walletdir>/database/log.?????????? files. | create a wallet directory at the specified location (containing a wallet.dat | ||||
No newline at end of file | data file, a db.log file, and database/log.?????????? files) instead of just | ||||
creating a data file at the path and storing log files in the parent | |||||
directory. This should make backing up wallets more straightforward than | |||||
before because the specified wallet path can just be directly archived | |||||
without having to look in the parent directory for transaction log files. | |||||
For backwards compatibility, wallet paths that are names of existing data | |||||
files in the `-walletdir` directory will continue to be accepted and | |||||
interpreted the same as before. | |||||
- When bitcoin is not started with any `-wallet=<path>` options, the name of | |||||
the default wallet returned by `getwalletinfo` and `listwallets` RPCs is | |||||
now the empty string `""` instead of `"wallet.dat"`. If bitcoin is started | |||||
with any `-wallet=<path>` options, there is no change in behavior, and the | |||||
name of any wallet is just its `<path>` string. | |||||
No newline at end of file |