Bitcoin-Qt wallet backup / Dogecoin hashrate wallet

Wallet Update (Non-Mandatory – Not a Hard Fork) – Heartbleed Fixed

VirusTotal Result – 0/51 : Click

– Only real change is the OpenSSL version used (patched yesterday to account for Heartbleed), but still worth staying safe and testing/backing up.

We still always recommend you keep a backup of your wallet.dat file.

We’ve been quietly working away in the background on a number of wallet/code upgrades – source, design as well as functionality (hints for future). Something we like to keep quiet because we work slow, cautiously and meticulous when it comes to certain things (anything remotely related to wallets or hard-fork decisions). I think that’s become a little clear. However the recent Heartbleed bug (ouch) obviously immediately made us apply a non-mandatory update to the code and Windows wallet (the others coming, hopefully we can find someone happy to share a build).

Some info. taken from another thread on Heartbleed and crypto wallets:
If you are using any other version of Bitcoin-Qt/Bitcoin Core, including bitcoind 0.9.0, you are vulnerable only if the rpcssl command-line option is set. If it is not, then no immediate action is required. If it is, and if an attacker could have possibly communicated with the RPC port, then you should consider your wallet to be compromised.

This vulnerability is caused by a critical bug in the OpenSSL library used by Bitcoin Core. Successfully attacking Bitcoin Core by means of this bug seems to be difficult in most cases, and it seems at this point that even successful attacks may be limited, but I recommend taking the above actions just in case.

All versions of Bitcoin-Qt are affected by the rpcssl part of the vulnerability if they are linked with an affected OpenSSL version.

Bitcoin has just patched to 9.1 to resolve Heartbleed, as well as a few other alts we can see. It’s not really a big deal to patch but something we took quite seriously. We’ve covered the bases as far as we’re aware concerning an OpenSSL upgrade that resolves the issue, but if anyone wants to give more feedback on our source we’re all ears. Rushing anything really irks me but looks like we’re in the clear.