This is a new minor version release that fixes bugs that were inherited from upstream Bitcoin and Namecoin code.

All users, on all platforms, are strongly recommended to upgrade.

Please see the release notes for further information.

This is a new minor version release including important bugfixes to networking code.

All users, on all platforms, are strongly recommended to upgrade.

A full description of all changes is available in the release notes

Note: availability of a notarized MacOS dmg is delayed due to a hiccup in the interaction with Apple's service, but it is expected to be provided at a later time. The unsigned, fully reproducible built MacOS version is available.

Important bugfixes

• Reduced peer inv object counts
• Improved transaction request tracking
• Improved orphan transaction handling
• Reduced getheaders traffic for inv messages
• Improved reporting of difficulty adjustment errors

Updates to pinned dependencies

• Updated freetype to version 2.11.0
• Updated expat to version 2.6.2

This is a new minor version release, including enhancements to several RPC methods and important security updates for Dogecoin-Qt.

Dogecoin-Qt users on any platform are strongly recommended to upgrade.

A full description of all changes is available in the release notes

Security Updates

• Disable BIP-70 payment server by default
• Reduce the build scope of the Qt dependency
• Backport patches for all Qt versions until 5.15.12 + community patches to the pinned Qt 5.7.1
• Added security guidance to INSTALL.md
• Updated the rpcuser.py script to improve the password and salt generation methods it uses

Enhancements

• estimatefee and estimatesmartfee are now maintained and tuned to Dogecoin parametrization
• Added fully verbose transaction decoding to getblock
• Added a height parameter to -walletnotify
• Added the getblockstats RPC method

RPC Changes

• verbosity parameter to getblock now accepts both integers and booleans
• Added a height parameter to importpubkey and importaddress

Translation Updates

• Chinese
• Dutch
• French
• French-Canadian
• Italian
• Korean
• Polish

Updates to pinned dependencies and subtrees

• Updated the depends, CI and build system to Ubuntu Focal
• Updated expat to version 2.5.0
• Updated the secp256k1 subtree to 44c2452
• Updated zlib to version 1.3
• Updated protobuf to version 3.6.1
• Updated fontconfig to version 2.12.6
• Removed dependency on libx11

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.

A full description of all changes is available in the release notes

Security-related fixes

This release contains multiple security related fixes:

• The alert system has been removed and processing of alert messages has been disabled
• The transaction download system has been made more reliable
• The protocol implementation has been amended to reject buggy or malformed messages
• Memory management in events of high network traffic or when connected to extremely slow peers has been improved

Fee Recommendation

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.

Breaking changes

• The behavior of the dumpwallet and backupwallet RPC methods, to exclusively write to the directory specified by -backupdir and no longer overwrite files
• The maximum number of addnode records that a node will track has been limited to 800

New features

• A new RPC method, liststucktransactions 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.
• Pruning configuration has been added to the UI, to make it easier to save diskspace for users of graphical (wallet) installations.
• 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 allowing for more fine-grained control of the node's network capacities.
• The graph in the UI's traffic monitor has been significantly improved by keeping track of the traffic we see in the background and then rendering it on demand, at any desired scale.
• 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.
• 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.

Translation updates

• Bulgarian
• Dutch
• French
• Italian
• Korean
• Persian
• Portuguese (pt_PT)
• Tamil

RPC API Changes

• The verifychain RPC command no longer accepts negative values
• addnode will now return error -32 when the address provided is too long
• getpeerinfo provides 2 new fields per peer, addr_processed and addr_rate_limited

Dependency updates

• Updated zlib to 1.2.12.
• Updated libevent to 2.1.12-stable.
• Update the LevelDB subtree to use the same version as Bitcoin 22.0, from the bitcoin-core maintained fork.

This is a new minor version release, including important security updates and changes to network policies. All Dogecoin Core users, miners, services, relay operators and wallet users are strongly recommended to upgrade.

This release can be installed over an existing 1.14 installation seamlessly, without the need for uninstallation, re-indexation or re-download. Simply shut down your running Dogecoin-QT or dogecoind, perform the installation and restart your node.

Important Security Updates

This release contains fixes for 2 high severity vulnerabilities that affect most Dogecoin Core users:

• Remote Code Execution in Dogecoin QT (CVE-2021-3401)
• Sensitive Information Exposure on Unix platforms (CVE-2019-15947)

Dogecoin QT (Graphical User Interface) users on all platforms and wallet users on the Linux platform are urged to please update their installations to this version immediately, to prevent malicious actors from exploiting these vulnerabilities.

Fee Reductions

This release finalizes a new minimum fee recommendation for all participants on the Dogecoin network, following the reduction of relay and mining defaults in 1.14.4. With this release, the minimum fees when creating transactions are recommended to be as follows:

• the recommended minimum transaction fee is 0.01 DOGE/kb, and
• the recommended dust limit is 1 DOGE, and
• the recommended RBF increment is 0.001 DOGE.

See the full recommendation here

RPC API Changes

• Added softdustlimit and harddustlimit fields to getnetworkinfo
• Added createauxblock and submitauxblock methods
• Added -rpcnamecoinapi that allows miners to use Namecoin-compatible AuxPoW APIs, for both getauxblock and createauxblock methods.

Other notable changes

• Updated Berkely DB to 5.3 and OpenSSL to 1.0.2u.
• The version displayed on QT's overview page has been changed to display the full version
• Updated the HD wallet derivation path to be compliant with SLIP44
• Updated the FreeBSD build.
• Added xkbcommon 0.8.4 as a separate dependency to fix keyboard compatibility issues
• Added a getting started guide

See the release notes for a full description of this release.

This is a new minor version release, including various bugfixes and performance improvements. It is a recommended update for all users.

This release can be installed over an existing 1.14 installation seamlessly, without the need for uninstallation, re-indexation or re-download. Simply shut down your running Dogecoin-QT or dogecoind, perform the installation and restart your node.

Enabling Future Fee Reductions

Prepares 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 - a followup release will implement the lower fee recommendation, once the network has adapted to the relay defaults introduced with this version of Dogecoin Core.

Synchronization Improvements

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 time has been reduced by around 2.5 times.

RPC Improvements

getpeerinfo now includes feefilter value for each peer, to be able to diagnose transaction relay issues.

Other notable changes

• Proactively disconnect peers sending block headers which would build on an invalid chain.
• Improve handling and logging of invalid blocks and their descendants
• Add menu option to import a private key
• Add column to peers table showing bytes sent/received, accessible via "Debug Window" from the "Help" menu.
• Add GUI for adding peers manually, accessible from the peers table of the Debug Window.
• Regtest network can now generate AuxPoW blocks.
• Corrections to French Canadian, Chinese, German, Indonesian, Korean, Polish and Portuguese translations

This is a new minor update that includes important performance improvements. It is a strongly recommended update for everyone.

This release can be installed over an existing 1.14 installation seamlessly, without the need for uninstallation, re-indexation or re-download. Simply shut down your running Dogecoin-QT or dogecoind, perform the installation and restart your node.

Improve synchronization speed

Significantly improves the speed at which a node can upload blocks, by removing expensive integrity checks that were performed each time a block is sent to another node. When a block is received and during rescans of the locally stored blockchain, the checks are still performed.

Reduce default mempool expiry time

Reduces the default time that transactions are cached in the mempool from 336 hours to 24 hours. 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.

Other changes and improvements

• Increase block download timeouts
• Add size_on_disk, prune_target_size, automatic_pruning to getblockchaininfo
• Add query options to listunspent RPC call
• Set BIP65 softfork heights in chainparams.cpp.
• Update package links for OSX cross compilation.
• Change IPC prefix from bitcoin: to dogecoin:.
• Locale independent sorting.
• Corrections to Italian translation.
• Refresh main and test network checkpoints and seeds.
• Do not print an error on connection timeouts through proxy.
• Numerous fixes to automated tests.
• Numerous fixes to documentation.

All users are encouraged to upgrade to this version, it includes an important bugfix to 1.14.0, and enables support for OP_CHECKLOCKTIMEVERIFY compared to pre-1.14.0.

This is a bugfix release which:

• Reverts a change of behaviour in the getauxblock command. The target field was renamed to _target in Namecoin and this change should not have appeared in Dogecoin, for compatibility with previous mining pool configurations. This has now been corrected.
• Fix description of supermajority based forks in getblockchaininfo - the full block version number was used instead of just the last byte, which made it appear forks were triggered early.
• Change references to "Bitcoin" to "Dogecoin" - these weren't user visible, but are done for consistency.
• Corrects the handling of so-called dust outputs in regards to calculating fees. This fixes an issue where a change output smaller than 1 DOGE would create a transaction that was not going to be relayed.

Note: We have skipped 1.14.1 as the last bug and its fix were found after 1.14.1 was tagged already.

This is the long awaited Dogecoin Core 1.14!

Please make sure, if you upgrade an existing version, to make a (current!) backup of your wallet.dat file! We have successfully upgraded existing wallets in our testing, but you should always keep a backup of that file regardless.

This version contains a soft fork to enable BIP-65 (OP_CHECKLOCKTIMEVERIFY). The fork is locked in at 750 of the previous 1000 blocks. At 950 of the previous 1000 blocks with base version 4, the client will start to reject blocks with a base version of <= 3. For pool operates this means that they should update to the final 1.14 version once it is released asap, but at least before the fork is activated to not risk mining invalid blocks after 95% of the mined blocks are on base version 4. While this is not very relevant to end users you should still make sure to update to 1.14 final sooner than later.

Updating will also enable us to continue testing with the 1.17 client, so please do so.

Please note that getinfo is deprecated and will be removed in the next Dogecoin release. There are now several different commands that contain parts of that data instead. Please see the release notes for detail.

Full release notes are available at https://github.com/dogecoin/dogecoin/blob/master/doc/release-notes.md

This is the first release candidate of Dogecoin Core 1.14.

There have been only slight improvements compared to Beta 1, mainly fixing verification progress display and the fee calculation for transactions. Please make sure, if you upgrade an existing version, to make a (current!) backup of your wallet.dat file! We have successfully upgraded existing wallets in our testing, but you should always keep a backup of that file regardless.

This version contains a soft fork to enable BIP-65 (OP_CHECKLOCKTIMEVERIFY). The fork is locked in at 750 of the previous 1000 blocks. At 950 of the previous 1000 blocks with base version 4, the client will start to reject blocks with a base version of <= 3. For pool operates this means that they should update to the final 1.14 version once it is released asap, but at least before the fork is activated to not risk mining invalid blocks after 95% of the mined blocks are on base version 4. While this is not very relevant to end users you should still make sure to update to 1.14 final sooner than later.

Important notes:

Please do not mine on the production network with this release, as it would trigger a soft fork earlier than expected.