very currency
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:
The key tasks before the final 1.14 release include:
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:
Important notes:
The key tasks before the final 1.14 release include:
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:
The key tasks before the final 1.14 release include:
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.
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.
For further explanation of these, see the above mentioned Bitcoin release notes.
Dogecoin Core 1.10 introduces headers-first and parallel block synchronization to greatly reduce the initial blockchain synchronization time.
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.
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.
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.
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 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.
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:
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:
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.
For further explanation of these, see the above mentioned Bitcoin release notes.
Dogecoin Core 1.10 introduces headers-first and parallel block synchronization to greatly reduce the initial blockchain synchronization time.
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.
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.
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.
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:
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.
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.
For further explanation of these, see the above mentioned Bitcoin release notes.
Dogecoin Core 1.10 introduces headers-first and parallel block synchronization to greatly reduce the initial blockchain synchronization time.
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.
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.
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.
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
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.
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.
For further explanation of these, see the above mentioned Bitcoin release notes.
Dogecoin Core 1.10 introduces headers-first and parallel block synchronization to greatly reduce the initial blockchain synchronization time.
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.
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.
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.
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.