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.

This is the first beta release of Dogecoin Core 1.14.

The main changes since Alpha 4 include fixes for the macOS version and some branding issues we encountered while testing. This also marks the first binary release of Dogecoin Core 1.14. You will be able to download binaries and installer packages down below. 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.

This is the fourth alpha release of Dogecoin Core 1.14! It contains an important fix for https://nvd.nist.gov/vuln/detail/CVE-2018-17144 and anyone running an earlier alpha must upgrade. This also includes other changes from Bitcoin Core 0.14.0 to 0.14.3 and some tweaks to parameters for BIP0009 version bits.

In theory we have an OS X build ready to go, and are waiting for a pull request to merge the fixes, and we can then build the beta/release candidate (TBD) of 1.14.

Important notes:

• This is not a binary release, you must be comfortable compiling it yourself.
• Please do not mine on the production network with this release, as it would trigger a soft fork earlier than expected.

This is the third alpha release of Dogecoin Core 1.14! It contains an important bugfix from the previous alpha, and you are recommended to upgrade. This update changes the default transaction version generated from 2 to 1, so that they are understood by 1.10 clients. Previously the transactions were ignored by old clients and therefore never mined on the production network. We'll update to version 2 transactions in a later release.

The alert system has also been re-added to this version, and live money tests have started with this version. It's essentially a beta candidate, although further cleanup is expected before there is a formal beta.

Important notes:

• This is not a binary release, you must be comfortable compiling it yourself.
• Please do not mine on the production network with this release, as it would trigger a soft fork earlier than expected.

The key tasks before the final 1.14 release include:

• Update Gitian builds to support OS X.
• Stress test the release on the test network.
• Hard disable (i.e. rip out) upgrading via version bits as it poses a risk to AuxPoW if there's any mistakes in it being disabled currently.

This is the second alpha release of Dogecoin Core 1.14! It contains two important bugfixes compared to the first alpha, and anyone on 1.14-alpha-1 should upgrade immediately. The major changes are:

• Fee rounding is now applied consistently across the code base by applying it in the fee rate rather than in the calling code (which had lead to some calls being missed).
• Coinbase maturity checks are now enforced correctly.

Important notes:

• This is not a binary release, you must be comfortable compiling it yourself.
• At the moment we expect to re-introduce the alert system into 1.14 before release, please disregard the release notes that discuss its deprecation/removal.
• Don't use this with money you aren't willing to lose. This is the version the developers will start doing mainnet currency tests with, however we'll be keeping amounts very small until there's a beta.
• Please do not mine on the production network with this release, as it would trigger a soft fork earlier than expected.

The key tasks before the final 1.14 release include:

• Update Gitian builds to support OS X.
• Re-introduce and test the alert system.
• Stress test the release on the test network.
• Hard disable (i.e. rip out) upgrading via version bits as it poses a risk to AuxPoW if there's any mistakes in it being disabled currently.

This is the first alpha release of Dogecoin Core 1.14! It has known limitations that need to be addressed before a release version, in particular around the fee calculations, however it is ready for testing by a wider audience than the Dogecoin developers.

Important notes:

• This is not a binary release, you must be comfortable compiling it yourself.
• At the moment we expect to re-introduce the alert system into 1.14 before release, please disregard the release notes that discuss its deprecation/removal.
• You should not use this with Dogecoin on the main network; it is intended for transactions on the testnet, and block verification/relaying on production. Please wait for a beta before using with real money.
• Please do not mine on the production network with this release, as it would trigger a soft fork earlier than expected.

The key tasks before the final 1.14 release include:

• Complete an audit of the RPC tests to identify why the remaining tests fail, and correct the test or code as applicable.
• Update Gitian builds to support OS X
• Re-introduce and test the alert system
• Stress test the release on the test network

Dogecoin Core 1.8.3 is a security release for those who cannot upgrade to Dogecoin Core 1.10 ONLY. It fixes a remote security hole in miniupnpnc, as well as issues in regards to an upcoming announcement of possible DoS vulnerabilities. See the announcement on the bitcoin-dev mailing list for reference. It is strongly recommended to upgrade your installation in case you run a node open to inbound connections from the internet.

If you cannot upgrade to Dogecoin Core 1.10, you MUST update to 1.8.3 to remain secure.

Dogecoin Core Release Notes

Pull in patches from upstream to mitigate the risk of a DoS attack.
Update the DNS seeds for more reliable bootstrapping of the initial peer discovery.
Update the list of fixed nodes, in case all other means of peer discovery fail.
Update to latest miniupnpc, which fixes a security hole

Credits

Listed in strictly alphabetical order, using name listed in Github. This
includes those whose contributions to Bitcoin Core have been merged
into this Dogecoin Core release:

P. Kaufmann
Max K.
Ross Nicoll
Wladimir J. van der Laan
Pieter Wuille

This is an alternative version of Dogecoin Core 1.10 with modifications to make it compatible with Dogeparty. Specifically, this adds support for address indexing and the "searchrawtransactions" RPC command. You should use Dogecoin Core 1.10 unless you need these extensions, as it has undergone further testing.

Dogecoin 1.10 is a complete rebuild based on Bitcoin 0.11. This means in terms of the code-base we introduced all the changes between Bitcoin 0.9 and 0.11 into this version of Dogecoin Core.
We therefore suggest to read the release notes of both Bitcoin 0.10 and Bitcoin 0.11. 1.10 is a recommended update for all users, and if you cannot update to 1.10 for whatever reason, you must update to 1.8.3 which is a critical security fix to 1.8.2.

Upgrading

To upgrade from any version below 1.10 you will need to re-index once, as the block database format has changed. If you run the Qt GUI client, it will prompt you to do so on the first start after the update. If you run a dogecoind daemon, you will need to start it with the parameter -reindex once after you updated. This process can take a few hours, depending on the performance of your machine.

IMPORTANT: During reindex transactions will be "replayed" by the wallet as they're indexed, meaning that your balance will not necessarily be accurate until the end of the reindex process. Do not send transactions during reindex, as this may result in conflicted transactions once the reindex is complete.

Notable changes

For further explanation of these, see the above mentioned Bitcoin release notes.

Faster synchronization

Dogecoin Core 1.10 introduces headers-first and parallel block synchronization to greatly reduce the initial blockchain synchronization time.

Watch only address support

It is now possible to add public keys to your wallet that will be held in a "watch only" state. This means you will get information about incoming/outgoing transactions and resulting balance changes. Especially useful to keep track of your paper wallets.

Strict signature encoding (BIP66)

This release activates BIP66 which enforces strict rules about how transaction signatures are encoded and therefore will introduce a new block version (3). These rules will only activate once a certain number of blocks are mined with this new version. NOTE: This is not a hard fork, as all existing wallets will accept version 3 blocks, although they'll fail to enforce the new requirements.

Block file pruning

It is possible to run a Dogecoin node without keeping the full blockchain on your disk. This is currently incompatible with having a wallet on that client due to the fact that some actions regarding a wallet require the full block data. The minimum amount of kept blocks has been changed from Bitcoin to reflect our shorter block times.

General comments

Please backup your wallet regularly and especially before performing this upgrade. Do not copy your wallet.dat while Dogecoin Core is open. Instead you should either use the backup feature you find in the "File" menu or shut down Dogecoin Core completely before you make a copy of your wallet.dat.

Dogecoin Core 1.8.3

Dogecoin Core 1.8.3 is a security release. It fixes a remote security hole in miniupnpnc, as well as issues in regards to an upcoming announcement of possible DoS vulnerabilities.
See the announcement on the bitcoin-dev mailing list for reference.
It is strongly recommended to upgrade your installation in case you run a node open to inbound connections from the internet.
If your installation is not open to incoming connections this update is not mandatory, but we still recommend keeping your client up to date.

Dogecoin Core Release Notes

• Pull in patches from upstream to mitigate the risk of a DoS attack.
• Update the DNS seeds for more reliable bootstrapping of the initial peer discovery.
• Update the list of fixed nodes, in case all other means of peer discovery fail.
• Update to latest miniupnpc, which fixes a security hole

Credits

Listed in strictly alphabetical order, using name listed in Github. This
includes those whose contributions to Bitcoin Core have been merged
into this Dogecoin Core release:

• P. Kaufmann
• Max K.
• Ross Nicoll
• Wladimir J. van der Laan
• Pieter Wuille

Dogecoin 1.10 is a complete rebuild based on Bitcoin 0.11. This means in terms of the code-base we introduced all the changes between Bitcoin 0.9 and 0.11 into this version of Dogecoin Core.
We therefore suggest to read the release notes of both Bitcoin 0.10 and Bitcoin 0.11. 1.10 is a recommended update for all users, and if you cannot update to 1.10 for whatever reason, you must update to 1.8.3 which is a critical security fix to 1.8.2.

This first release candidate introduces a number of bug fixes and improvements since beta 2:

• Correct icon in Help menu for About option
• Enforce low-S encoding on transactions to be relayed, to eliminate that form of transaction malleability
• Correct some regressions in operation of AuxPoW mining
• Update to latest version of miniupnpc (critical security fix!)
• Switch available units to Doge, kDoge and mDoge.

Upgrading

To upgrade from any version below 1.10 you will need to re-index once, as the block database format has changed. If you run the Qt GUI client, it will prompt you to do so on the first start after the update. If you run a dogecoind daemon, you will need to start it with the parameter -reindex once after you updated. This process can take a few hours, depending on the performance of your machine.

Notable changes

For further explanation of these, see the above mentioned Bitcoin release notes.

Faster synchronization

Dogecoin Core 1.10 introduces headers-first and parallel block synchronization to greatly reduce the initial blockchain synchronization time.

Watch only address support

It is now possible to add public keys to your wallet that will be held in a "watch only" state. This means you will get information about incoming/outgoing transactions and resulting balance changes. Especially useful to keep track of your paper wallets.

Strict signature encoding (BIP66)

One of the reasons why mining is disabled on this release is the introduction of BIP66 which enforces strict rules about how transaction signatures are encoded and therefore will introduce a new block version (3). These rules will only activate once a certain number of blocks are mined with this new version. To not let this happen too early, mining is disabled for now. NOTE: This is not a hard fork, as all existing wallets will accept version 3 blocks, although they'll fail to enforce the new requirements.

Block file pruning

It is possible to run a Dogecoin node without keeping the full blockchain on your disk. This is currently incompatible with having a wallet on that client due to the fact that some actions regarding a wallet require the full block data. The minimum amount of kept blocks has been changed from Bitcoin to reflect our shorter block times.

General comments

Please backup your wallet regularly and especially before performing this upgrade. Do not copy your wallet.dat while Dogecoin Core is open. Instead you should either use the backup feature you find in the "File" menu or shut down Dogecoin Core completely before you make a copy of your wallet.dat.

Dogecoin 1.10 is a complete rebuild based on Bitcoin 0.11. This means in terms of the code-base we introduced all the changes between Bitcoin 0.9 and 0.11 into this version of Dogecoin Core.
We therefore suggest to read the release notes of both Bitcoin 0.10 and Bitcoin 0.11

Beta 2 introduces a number of bug fixes and improvements since beta 1:

• Correct AuxPoW support checks to match Dogecoin Core 1.8 rather than Namecoin
• Correct and expand RPC unit tests
• Add NODE_BLOOM service bit
• Fix missing new line in error messages
• Update testnet checkpoints so syncing is smoother, and add DNS seed
• Correct incompatibilities in fee calculation code compared to Dogecoin Core 1.8
• Remove old Bitcoin release notes
• Replace further references to Bitcoin with Dogecoin where user-facing
• Use locale-specific number formatting instead of thin spaces as thousand-separator in numbers

Upgrading

To upgrade from any version below 1.10 you will need to re-index once, as the block database format has changed. If you run the Qt GUI client, it will prompt you to do so on the first start after the update. If you run a dogecoind daemon, you will need to start it with the parameter -reindex once after you updated. This process can take a few hours, depending on the performance of your machine.

Mining

For this beta release, we decided to disable AuxPoW mining, while further testing is completed. The functionality will be re-enabled in a later release candidate.

Notable changes

For further explanation of these, see the above mentioned Bitcoin release notes.

Faster synchronization

Dogecoin Core 1.10 introduces headers-first and parallel block synchronization to greatly reduce the initial blockchain synchronization time.

Watch only address support

It is now possible to add public keys to your wallet that will be held in a "watch only" state. This means you will get information about incoming/outgoing transactions and resulting balance changes. Especially useful to keep track of your paper wallets.

Strict signature encoding (BIP66)

One of the reasons why mining is disabled on this release is the introduction of BIP66 which enforces strict rules about how transaction signatures are encoded and therefore will introduce a new block version (3). These rules will only activate once a certain number of blocks are mined with this new version. To not let this happen too early, mining is disabled for now. NOTE: This is not a hard fork, as all existing wallets will accept version 3 blocks, although they'll fail to enforce the new requirements.

Block file pruning

It is possible to run a Dogecoin node without keeping the full blockchain on your disk. This is currently incompatible with having a wallet on that client due to the fact that some actions regarding a wallet require the full block data. The minimum amount of kept blocks has been changed from Bitcoin to reflect our shorter block times.

General comments

Please backup your wallet regularly and especially before performing this upgrade. Do not copy your wallet.dat while Dogecoin Core is open. Instead you should either use the backup feature you find in the "File" menu or shut down Dogecoin Core completely before you make a copy of your wallet.dat.