doc/release-notes/release-notes-1.14.3.md
Dogecoin Core version 1.14.3 is now available from:
https://github.com/dogecoin/dogecoin/releases/tag/v1.14.3/
This is a new minor version release, including various bugfixes and performance improvements. It is a recommended update for all users.
Please report bugs using the issue tracker at github:
https://github.com/dogecoin/dogecoin/issues
To receive security and update notifications, please watch reddit or Twitter:
The developers also maintain personal Twitter accounts:
Dogecoin Core is extensively tested on Ubuntu Server LTS, Mac OS X and Windows 10.
Microsoft ended support for Windows XP on April 8th, 2014, No attempt is made to prevent installing or running the software on Windows XP, you can still do so at your own risk but be aware that there are known instabilities and issues. Please do not report issues about Windows XP to the issue tracker.
Dogecoin Core should also work on most other Unix-like systems but is not frequently tested on them.
When loading block headers to send to a peer, the block was revalidated by calculating its proof of work. This is expensive and led to a bottleneck in the sync process where nodes were CPU rather than IO bound in sending blocks to ther peers.
All block headers are already checked when they are accepted, and they will be checked again on the receiving node.
Reduces DEFAULT_MEMPOOL_EXPIRY from 336 hours to 24 hours. Motivation is that while blocks are empty, un-relayable tx are stuck in mempools for a long time and effectively locking utxo for 2 weeks until they can be respent, if no RBF opt-in was performed (most wallet implementations do not do RBF opt-in.)
As the expectation is that block space will not be fully utilized for the foreseeable future, and therefore, as long as this is the case, no valid transaction should ever live in the mempool for more than a couple of minutes.
This default setting can be overridden with the -mempoolexpiry parameter by individual node operators to a value (expressed in hours) that makes the most sense for the use cases the node serves.
Block download timeouts are expressed as a multiple of block interval, and as such Dogecoin block download times were relatively aggressive, leading to a high number of timeouts. Increased the timeouts to be more flexible to real world conditions.
bitcoin: to dogecoin:.Thanks to everyone who directly contributed to this release: