Miners are free to do this - and some may already be doing this (I am not 100% certain if that is the case though).

They have already fixed the code - the main issue now is that people have not "refreshed their browser pages" who were using the buggy code (and of course the funds that have not been swept from the compromised keys) and people still using compromised addresses (I am assuming that blockchain.info would have sent all affected users an email - but not all may have received that email or acted on it).

This is not a swastika but a Buddhist symbol (the swastika is the mirror image - i.e. to the right not the left) and it is not (nor ever has been) a Chinese character.

If you travel around Asia you'll see the above symbol at many Buddhist temples but you won't see the "swastika" at all (although maybe the swastika symbol had some other European usage before Hitler).

It is less and less popular for Chinese to eat dog (or cat) meat these days as Chinese are actually very keen pet owners - so although some (generally small non-chain) restaurants still have such "fragrant meat" (as it is often referred to) dishes they are most definitely on the decline.

Very few large chain restaurants (which are considered "upscale restaurants" in China) have dog or cat meat on their menus now.

Oh - and how do I know this? I have lived in China for 8 years (and resided in various different cities).

The file size shouldn't be very big (unless your wallet has a large number of keys).

Basically the only file that matters is wallet.dat - so just make sure you have that backed up and you will be fine (of course don't forget your passphrase otherwise the backup is useless assuming you have used a secure passphrase which you should).

I'm not sure if Bitcoin Core has a restore from backup in the UI - but if you ever need to do that you'll find forum members that will help you (so just make sure you keep the backup).

Also - as Bitcoin Core does not use a "seed" you need to make regular backups of your wallet (depending upon how many txs you do) - I'd recommend taking a new backup at least once per week.

Perhaps try File -> Backup Wallet?

(am going from memory but I think that is where it is)

The incredible incompetence is not the fact that a variable was uninitialised but the fact that this code made it into production.

Unlike most devs who post in this forum I have worked on security software and also financial software (at the level that is used to run an entire insurance company).

Such bugs never happen there (as anything that is critical is checked by senior programmers well before being released - this clearly did not happen at blockchain.info).

I have not made an uninitialised variable mistake in over 10 years (and I code in C++ where this can be a serious issue).

For code to have been released into production with such a mistake is *clearly incompetence* and I am not talking about the particular dev (everyone makes mistakes) but by the organisation itself (where was the code review?).

You can't promote yourself to be a secure website for storing money if you can't even manage to audit simple code issues like initialisation.

My recommendation would be not to use blockchain.info for storing funds - they are clearly not up to the job of actually securing it.

Sorry - but we ended up with one of those typically aggressive shills attacking the other topic so I have started this one.

Those that seriously want to talk about AT and ACCT should post here (I'll delete any shill posts).

Thread closed due to Nxt shill.

We can start a new topic but self-moderated to keep out the assholes.

So I have reported the Nxt *shill* to the mods.

You can keep being a retard and posting here - I'll just lock the thread as we aren't going to tolerate the Nxt nonsense here (there is a very good reason why AT will never appear on Nxt).

Off topic posts will be reported - your last warning.

I see - you are in the wrong topic.

This topic is about AT not about Jl777 and his legion of fans.

If you persist with these off topic posts they will be reported.

Seriously - I am not interested in anything a guy who doesn't even understand the problems that binary floating point has (and you should be more wary of such people also).

Atomic cross-chain transfer was invented by BTC forum member TierNolan - so I suggest you educate yourself rather than being a *fan boy of Jl777* and I don't think you'll find anyone here is interested in "Supernet".

Bitcoin development is now very conservative so I would not be too worried about that - if there was any reason why addresses would need to be changed (such as ECDSA being cracked) then I'm sure you'll know about it before it is too late.

My guess is that you are *learning* now - so do some more research into cold storage in order to properly secure your BTC (and there are numerous forum members who can help guide you here).

If you are changing your passphrase for your bitcoin-qt wallet then you will still need to move all your balance to a new address (assuming your concern is someone being able to crack your old passphrase).

I am pretty sure that the unused private keys in your key pool are discarded at the point of changing your passphrase so after changing the passphrase (and making sure you keep a backup of your old wallet) send the funds to a new address (and of course backup again).

And as others have already pointed out - bitcoin-qt can't do cold storage unless you are running it from a computer that isn't connected to the internet.

You question is completely flawed as 100 online wallets could do things in 100 different ways.

You might want to think about your question a bit more if you want a serious answer.

One other simple approach is to use something like blockchain.info to see if the tx has been at least picked up (you can right click on the transaction and copy its transaction id - when pasting that into blockchain.info just remove the dash and 3 digits it puts on the clipboard at the end).

Why exactly would you want to get uncompressed ones?