doc/release-notes/release-notes-1.14.6.md
Dogecoin Core version 1.14.6 is now available from:
https://github.com/dogecoin/dogecoin/releases/tag/v1.14.6/
This is a new minor version release, including important security updates and changes to network efficiency. All Dogecoin Core users - miners, services, relay operators and wallet users - 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
Releases are also announced on reddit:
https://www.reddit.com/r/dogecoindev/
Dogecoin Core is extensively tested on Ubuntu Server LTS, Intel-based macOS and Windows 10.
Dogecoin Core should also work on most other Unix-like systems but is not frequently tested on them.
This release contains fixes that harden node and network security. These fixes are important for every node operator and wallet user.
The P2P alert system has been removed and alert messages are no longer processed. This was planned for the next major release, but as bugs were found in the implementation, the full deprecation of this feature has been executed early, because it makes no sense to overhaul a system that is unused and already marked for removal in the near future.
Significantly reduce the impact of peers that withhold transaction information (accidentally or otherwise) in the announcement stage, before the transaction is mined, by enforcing strict controls, limits and timeouts on all transaction announcements and giving preference to outgoing connections when deciding which peer to request transaction information from.
This improves the resilience of the entire network and improves reliability of transaction relay throughout.
This release changes the recommended dust limit for all participants on the Dogecoin network from 1 DOGE to 0.01 DOGE. The full recommendation can be found in the documentation.
This change has been implemented in the wallet as the default value of
-discardthreshold, resulting in the following default logic:
Adds a new command line parameter -backupdir that allows operators to specify
where to store wallet backups and dumps. When not set, the node will add a
directory under the data directory called "backups".
This is a breaking change.
The behavior of the dumpwallet and backupwallet RPC methods has changed, as
these will ignore any path given other than the filename, and will always store
the filename in the directory defined with -backupdir or the above-mentioned
default location.
These methods will also refuse to overwrite any existing files and will produce error messages to that effect.
To protect against users accidentally submitting an insane amount of address
records using the addnode RPC call, the maximum number of "addnode" records
has been limited to 800, which is 100x the maximum number of manually added
nodes that the software connects to (8).
Once this maximum is reached, the software will refuse to add any more addresses and return an error.
Users can remove existing addnode records from the software by running:
dogecoin-cli addnode <address> remove
A new RPC method has been added to help wallet operators identify if any transactions are stuck (have not been mined and are not in the mempool) and enable resolution. This helps in cases where node-local fee or dust policies change, to prevent the node from sending out old transactions that got lost.
The method can be called with:
dogecoin-cli liststucktransactions
Adds pruning configuration to the UI, to make it easier to save diskspace for users of graphical (wallet) installations. Before, this could only be done through manual editing of the configuration file.
The new setting allows a user to decrease the total disk space used for keeping full blocks the node down to 3GB, by removing blocks that are no longer needed for full incremental validation of the blockchain.
Caveats
Note that when running a pruned node, the following applies:
A new RPC method setmaxconnections has been introduced that enables wallet
and node operators to change the maximum number of connections their node
allows without needing to restart (and with that, lose all connections)
allowing for more fine-grained control of the node's network capacities.
The node will allow reducing the number of connections until a minimum of 28, and will automatically adapt to a maximum that the host OS allows.
To change the maximum number of connections, run:
dogecoin-cli setmaxconnections <desired_amount>
Significantly improves the graph in the UI's traffic monitor by not throwing away data every time the graph scale got resampled, but instead keeping track of the traffic we see in the background and then rendering it on demand.
A new RPC method, rescan, has been added to allow node operators to rescan
the chain for wallet transactions from a certain height. This can help speed
up the rescan process for keys that are known to be generated after a certain
date or block height, as older blocks do not necessarily require to be scanned
in that scenario. This may also be helpful when adding large quantities of
watchonly addresses.
NOTE: rescanning the blockchain takes a lot of time.
To use the rescan functionality, use:
dogecoin-cli rescan <start_block>
It will inform of the state before and after when the process finishes:
{
"before": {
"balance": 69.00000000,
"txcount": 1
},
"after": {
"balance": 420.00000000,
"txcount": 3
},
"blocks_scanned": 31337,
"time_elapsed": 23
}
A new endpoint has been added to the REST server to find the current best known block at a certain height, without having to do RPC calls. This is useful for service implementations that need to track or query blocks.
The new endpoint can be queried with:
GET /rest/blockhashbyheight/<height>
Significant updates have been provided to the following languages:
Policies and tooling have been updated to enable translators better in their efforts to make Dogecoin more accessible to people that do not speak English.
verifychain RPC command no longer accepts negative valuesliststucktransactionssetmaxconnectionsrescanaddnode will now return error -32 when the address provided is too longgetpeerinfo provides 2 new fields per peer, addr_processed and
addr_rate_limited, that track addr message processingdumpwallet and backupwallet now write their output to the configurable
backup directory and do not overwrite existing files1.2.12.2.1.12-stable.22.0, from
the bitcoin-core maintained fork.gitian-build script to ease doing deterministic builds
for everyone, and the documentation of that process.Credit goes to all awesome contributors to this release, alphabetically: