doc/release-notes/release-notes-1.14.7.md
Dogecoin Core version 1.14.7 is now available from:
https://github.com/dogecoin/dogecoin/releases/tag/v1.14.7/
This is a new minor version release, including enchancements to several RPC methods and important security updates for Dogecoin-Qt. Dogecoin-Qt users on any platform are strongly recommended to upgrade.
Please report bugs using the issue tracker at GitHub:
https://github.com/dogecoin/dogecoin/issues
To receive notifications about updates, subscribe to the release mailing list:
https://sourceforge.net/projects/dogecoin/lists/dogecoin-releases
Dogecoin Core is extensively tested on Ubuntu Server LTS, macOS and Windows. Minimum OS compatibility can be found in the INSTALL guide.
This release contains fixes for Dogecoin Qt across all platforms that increase security for end users.
To mitigate future potential risk inside Dogecoin Qt, support for BIP-70 payment requests and related BIP-71 and BIP-72 payment URIs and MIME types have been disabled by default, because this functionality interacts with remote websites in an automated manner and could be used to amplify any future vulnerabilities inside Dogecoin Qt. By default, incoming BIP-70 payment requests and files or URLs that use the functionality are rejected and an explanation is shown to the user.
BIP-21 payment requests remain fully supported.
The functionality can be re-enabled by using enable-bip70=1 either in your
dogecoin.conf or as an argument to Dogecoin-Qt if absolutely needed. Please use
extreme caution when exercising this option.
This is step 1 in full deprecation of BIP-70, BIP-71 and BIP-72 inside Dogecoin Core. Future releases may completely remove this feature.
Implemented with #3412
rpcuser.py script to improve the password and salt generation
methods it uses (#3388). If you've used this script in the past, replacing
current authentication in dogecoin.conf with new credentials generated with
the new version of this script is recommended.Fee estimation was explicitly not ported or supported on Dogecoin Core since
1.14.0, but as the non-functional data from estimatefee and estimatesmartfee
were anyway used in the field, services using these RPC methods were unable to
provide fee estimates to their users. Therefore this feature has now been ported
to support Dogecoin parametrization.
The RPC methods estimatefee and estimatesmartfee are now under active
maintenance and will be further enhanced in the future.
NOTE: Because the minimum and maximum tracked fees and spacing of fee buckets
has changed, the fee_estimates.dat file from earlier versions will be
discarded after restarting this version of the software. This means that after
the first restart, the estimates will reset, but become usable again after the
node has processed a few blocks, and will improve in precision over up to 12
hours after the first restart. Any subsequent restarts will use the estimates
from the file as usual.
If you have in the past ran a custom compiled version of 1.14.7 or created
your own higher version, you must manually delete the fee_estimates.dat file
from your datadir for the new parametrization to take full effect.
Implemented with #3389 and #3433
getblockUpdates the getblock RPC to use verbosity levels 0-2 besides the existing
boolean. This allows operators to decode a full block in one go when using
level 2, instead of having to query getrawtransaction for each individual
txid returned with the boolean true.
Mapping between boolean and integer parameter functionality:
| Verbosity | boolean | level (int) |
|---|---|---|
| Hex encoded block | false | 0 |
| Block with txids | true | 1 |
| Block with decoded transactions | - | 2 |
For more information see:
dogecoin-cli help getblock
Implemented with #3299, #3306 and #3307
getblockstats RPC methodThe new getblockstats RPC method computes statistics for a given block hash if
the block is available on the node (pruned nodes can only run statistics over
blocks that aren't pruned.)
The user can select which stats are returned to save processing time for stats that aren't wanted. For more information, use:
dogecoin-cli help getblockstats
Implemented with #3297
height parameter to -walletnotifyAdds %i in the command to include the height of the block containing the
transaction. If the transaction is not in any block, the height is 0.
Implemented with #3257 and #3382
Updates have been provided to the following languages:
getblockstats (#3297)verbosity to be expressed as an integer to getblock and add full
verbosity under level 2 that serializes all transactions as JSON in the
reply (#3299, #3306, #3307)height parameter to importpubkey (#3102) and importaddress (#3235)
which allows the user to specify from which chain height to rescan for wallet
transactions.getmocktime (regtest-only) (#3322)NOTE: on systems that cannot use pinned dependencies from depends/, please
be aware that due to a bug in boost-1.83, building may lead to failure.
More information about the bug can be found at the boostorg/signals GitHub
repository at https://github.com/boostorg/signals2/issues/68.
-maxtxfee was not being respected outside of the wallet,
which caused problems with the sendrawtransaction RPC call. (#3088)dogecoind.service file (#3066)--enable-experimental) and enforce these at compile time (#3136).
See experiments.md for more information about which
experiments are available to self-compile.assumevalid to help new nodes save CPU time by setting it to block
e7d4577405223918491477db725a393bcfc349d8ee63b0a4fde23cbfbfd81dea, at height
5,050,000 on mainnet (#3416)ltc-scrypt module to a maintained fork (#3080), which
can be found at https://github.com/dogecoin/ltc-scryptrpcbind (#3228) and feefilter (#3241)Credit goes to all awesome contributors to this release, alphabetically: