doc/release-notes/release-notes-1.14.4.md
Dogecoin Core version 1.14.4 is now available from:
https://github.com/dogecoin/dogecoin/releases/tag/v1.14.4/
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:
Dogecoin Core is extensively tested on Ubuntu Server LTS, Mac OS X and Windows 10.
Dogecoin Core should also work on most other Unix-like systems but is not frequently tested on them.
This release preparing the network for a reduction of the recommended fees by reducing the default fee requirement 1000x for transaction relay and 100x for mining. At the same time it increases freedom for miner, wallet and node operators to agree on fees regardless of defaults coded into the Dogecoin Core software by solidifying fine-grained controls for operators to deviate from built-in defaults.
This realizes the first part of a two-stage update to lower the fee recommendation.
The main highlights for these enhancements are:
-mintxrelayfee=<amount> option.-blockmintxfee option.-dustlimit option.For this release, the recommended fees and dust limits, as implemented in the
wallet, remain at 1 DOGE per kilobyte, inclusive of the rounding up to the
nearest kilobyte, as miners and the relay network will upgrade gradually,
requiring time for transactions with lower fees to be able to be relayed and
mined. Not doing this would result in all transactions being rejected by old
nodes. A subsequent release will finalize the second stage and lower the
recommended fees implemented in the wallet by default. Wallet operators can
however, at their own judgement and convenience, change the fees paid from
their wallets with the -paytxfee=<amount per kb> option.
This release removes a bug in the network layer where a 1.14 node would open many parallel requests for headers to its peers, increasing the total data transferred during initial block download up to 50 times the required data, per peer, unnecessarily. As a result, synchronization has time has been reduced by around 2.5 times.
Additionally, when a node is in initial synchronization and a peer takes too long to respond to a new header request, it is now aggressively disconnected, to free connection slots for faster peers and not add more stress to already overloaded peers.
getpeerinfo now includes feefilter value for each peer, to be able to diagnose transaction relay issues.
contrib/seeds/generate-seeds.py.