very currency
Dogecoin Core 1.8.2 is a bugfix release. It updates OpenSSL to 1.0.1l, mainly fixing security issues.
The main takeaway is that builds from http://dogecoin.com are not affected. But if you build your own version, please make sure you update to 1.8.2 before updating your OpenSSL!
Please refer to this section in the Bitcoin Core release notes for further info: https://github.com/bitcoin/bitcoin/blob/0.9/doc/release-notes.md#openssl-warning
Listed in strictly alphabetical order, using name listed in Github. This includes those whose contributions to Bitcoin Core have been merged into Dogecoin Core:
Dogecoin Core 1.8.1 is primarily a bugfix release, bringing Dogecoin Core in line with Bitcoin 0.9.3. Dogecoin Core 1.8.1 also adds in support for printing paper wallets, and disables connections to pre-1.8 clients. This is a RECOMMENDED upgrade due to the large number of bug fixes, but is not a required one.
Paper wallet support has been developed by AndyMeows (IRC username), and can be accessed via the "File" menu. It's intended for two purposes; to generate small value paper wallets to hand out, and more permanent deposit paper wallets for keeping balances offline.
IMPORTANT: If you are producing offline paper wallets, you should do so on a computer that's disconnected from the Internet. While the wallet generator does not save the keys it generates, this ensures there is no risk of a virus or similar capturing the key from memory or interfering with its generation.
Full release notes for Bitcoin Core 0.9.3 are available from https://bitcoin.org/en/release/v0.9.3 , but highlights are included below:
There is a known issue with quantities in JSON used by the RPC interface (https://github.com/dogecoin/dogecoin/issues/134). This stems from the use of a floating point precision number to hold fixed precision data. Currently looking at solutions, which primarily either involve JSON which is not compliant to the specification, or making the RPC layer slightly incompatible with the conventional Bitcoin API.
This only affects values significantly below 1 Doge, however merchants may wish to round to the nearest Doge on all transactions for now.
Listed in strictly alphabetical order, using name listed in Github. This includes those whose contributions to Bitcoin Core have been merged into Dogecoin Core:
Dogecoin Core 1.8.1 is a non-mandatory update. It includes patches introduced by upstream Bitcoin 0.9.3 (see release notes here https://bitcoin.org/en/release/v0.9.3) and as a new feature integrated paper wallet printing support. It also blocks clients older than version 1.8 from connecting as these wouldn't be able to sync anymore anyway due to the introduction of AuxPoW. Several translations have been updated.
About paper wallet printing It is advised to print paper wallet on an offline computer. The client will warn you about that in case you are connected to the network.
Dogecoin Core 1.8 introduces AuxPoW from block 371,337. AuxPoW is a technology which enables miners to submit work done while mining other coins, as work on the Dogecoin block chain. Dogecoin Core 1.8 also enables payment protocol support for Dogecoin (note that Dogecoin's implementation of payment protocol is not compatible with Bitcoin's protocol). Lastly, 1.8 also includes all fixes from Bitcoin Core 0.9.2, whose release notes you can read at https://bitcoin.org/en/release/v0.9.2 (this is a summary, and the release includes around 150 bugfixes from Bitcoin Core).
Note that all users MUST upgrade to 1.8. If you're unable to update before the switchover block (371,337, expected around 12 September 2014), you MUST update as soon as possible afterwards in order to be able to continue to use Dogecoin. Users remaining on the previous client will not be able to receive or spend Dogecoin (with the exception of with other nodes who have not upgraded).
Before upgrading, back up your wallet.dat file just in case of any problems; you can back up the wallet.dat file by using the "Backup Wallet" option from the "File" menu. Ensure your existing wallet software is closed before upgrading.
Note that a full reindex is required as part of the upgrade to 1.8, and this will typically take around an hour to complete. If you are running the Qt client you will be prompted to reindex when first running the software, while if you use "dogecoind" you must run it the first time with the "-reindex" command line option.
To ensure a smooth switchover to AuxPoW, 1.8 has safe mode disabled 1 hour before until 24 hours after the switch block. This ensures the actually legit fork will not trigger safe mode and halt mining. If you don't want to have this behavior, then refer to the 1.8-safemode branch. This one doesn't include the patch to disable safe mode.
As 1.8 includes a substantial change to the mining protocol, downgrading to previous clients is not possible.
AuxPoW is enabled from block 371,337. Until that block the RPC commands for using AuxPoW will not function, and AuxPoW blocks will be rejected.
AuxPoW benefits Dogecoin in two ways; firstly, the effective hashrate of the coin is increased by these additional miners, making it harder to perform a 51% attack against the coin, and secondly it reduces conflict for resources (Scrypt miners), demotivating multipools from switching between Dogecoin and other Scrypt coins.
AuxPoW blocks are mined using the "getauxblock" and "getworkaux" RPC commands. Support for AuxPoW mining is included in Powerpool ( https://github.com/simplecrypto/powerpool/ ) and p2pool ( http://p2pool.in/ ).
In comparison to the AuxPoW implementation in United Scrypt Coin, Dogecoin uses a different coinbase transaction input script format which includes block height in compliance with BIP0034.
Dogecoin Core 1.8 adds payment protocol support, which is used to streamline payments being made to merchants.
This protocol is defined in DIP0070-DIP0072, based on the BIP standards with the same assigned numbers. DIP standards can be found at https://github.com/dogecoin/dips/ . The key differencs between the Bitcoin and Dogecoin payment protocols are that the Dogecoin payment request uses a "genesis" field containing the hash of the network's genesis block to identify networks instead of the "network" field. Further, MIME types for the request, payment and response are modified to identify the files as distinct types from the Bitcoin files.
As of 1.8 all transactions have fees applied by defaults, with no exemptions made for "old" coins. This ensures fees are consistent, while remaining extremely competitive (typically 1 Doge, or around $0.00012 per transaction).
The format of IP masks supplied to the "rpcallowip" command line option has changed. It no longer accepts subnets like '192.168..', and the format '192.168/16" should be used instead.
The Chinese and Korean translations have been updated.
Protocol version has been updated to 70003, meaning that a later release of the client can block access to all old clients (70002 and below).
In case of an error reading the block database from disk, the database cursor could be left open, which caused an assertion error later. The database cursor is now correctly disposed of in all cases.
Tweaked trigger conditions for safe mode to take into account the much faster block time of Dogecoin compared to Bitcoin. This should lead to less false positives.
A problem in parsing mangled dogecoin: URIs under Windows has been resolved, and as part of this work network detection for dogecoin: URIs is now more robust.
This is the first beta of Dogecoin Core 1.8.
It already has AuxPoW functionality built in. Starting block for testnet was 158,100, for mainnet it will be 371,337.
After you updated your client and start 1.8 the first time, the Qt client will prompt you for a reindex of the block data. It is important to accept this, as the format has changed. This takes, depending on your machine, somehwere around 15-30 minutes. It will not re-download the chain, just reindex your local copy. If you are running a daemon (dogecoind), then you need to manually start it with the -reindex parameter once!
Since the testnet already has AuxPoW enabled, you can start the client with the -testnet flasg and play around on it. You can mine directly into your wallet by pointing your miner to the IP of the wallet and port 44555. You may need to start it with -server and set a RPC user and password in the dogecoin.conf file.
If you are using the client on the testnet you might see fork warnings. In case your client goes into safe mode while playing on the testnet you can run it with -disablesafemode. We are working on making the transition on mainnet as smooth as possible for the final version.
This is a security release.
Dogecoin Core 1.7.1 is built against OpenSSL 1.0.1h, released to close recently disclosed vulnerabilities, which could have an impact on the usage of RPC over SSL. If you use this feature, it is advised that you upgrade to 1.7.1 and OpenSSL 1.0.1h.
If you do not use RPC over SSL, you don't need to upgrade.
No other changes where made in this release.
If you are still using Dogecoin Core 1.6 and also use RPC over SSL in a publicly accessible manner, we advise you to upgrade to 1.7.1 or restrict the usage of RPC to your local controlled network.
Dogecoin 1.7 is a complete re-architecture of the Dogecoin client, changing from using the Litecoin client as its base, to Bitcoin 0.9. It's still Dogecoin, same Scrypt PoW algorithm, same reward schedule, but there's a lot of changes under the hood.
For the full Bitcoin 0.9 changelog, please see https://bitcointalk.org/index.php?topic=522014
First and foremost, please note that downgrading from 1.7 to 1.6 is not trivial. 1.7 now uses Berkeley DB 5.1 as its default database (in place of 4.8), and as such may create database files which are incompatible with previous versions.
Following in the footsteps of Bitcoin (Core), the Dogecoin reference client has been rebranded as "Dogecoin Core". This helps separate its identity from Dogecoin (the network).
Where previously commands were sent to dogecoind by running
"dogecoind
This version is able to detect forks and warn about them both in the GUI and through calling the alertnotify script when a sufficiently long or invalid fork occurs.
For anyone running an exchange, please also note that in light of the 51% attack against Reddcoin last night, the Dogecoin developers now recommend a minimum of 10 confirmations for payments into an exchange.
This is Dogecoin 1.7.0 RC1. Following a run down of the changes since Beta 2:
This release mainly fixes a bug which could cause problems with spending coinbase (mined) transactions in Beta 1.
Changes:
Thanks to everyone who contributed!
For more information about the changes in 1.7, check the Alpha 1 release notes: https://github.com/dogecoin/dogecoin/releases/tag/v1.7.0-Alpha-1
This is Beta 1 of the all new Dogecoin Core 1.7.0 client.
This client runs on the production network by default. As always, please backup your wallet.dat.
Changes since Alpha 1:
For more information about the changes in 1.7, check the Alpha 1 release notes: https://github.com/dogecoin/dogecoin/releases/tag/v1.7.0-Alpha-1