if you can find the wallets then you can open them one by one in electrum and send the bitcoins to a wallet you do want to keep. you could even script this with the electrum command line. i don't think the other ways are practical.

are you indian? anyway if it's not the ssd then it could be ram. run mem test for a couple of hours.

Man these arguments were made before the recent halving and no doubt before previous halvings. They will be rolled out again before the next halving too. The answer to your question is that mining companies know full well when the halving is going to happen and they make their plans accordingly. There was no huge drop in hash rate after the recent halving like some had predicted.

The only dramatic event that took place was that the price doubled. So even though they are making less btc they are making more dollars.


It's gone from cents to the btc to hundreds of dollars to the btc. How can you say it hasn't appreciated in value?

exchanges probably use custom implementations. back in the day we learned that one of the reasons mt. gox lost so many bitcoins is because their custom implementation didn't keep up with patches to the satoshi client. I don't think the need for a custom version has changed so i think exchanges are still probably using a custom implementation because otherwise they couldn't keep up with the load.

if the QR code is not too blurred then scanning that might be a better idea than trying to brute force the priv key. QR codes have built-in redundancies and error correction so even a slightly damaged QR code can yield a lot, if not all, of the data.

The answer to your question is bloom filters. It's supposed to be a way to request transaction data from full nodes without revealing your addresses. Unfortunately the theory doesn't hold out in practice and it does leak out info about your addresses:

http://bitcoin.stackexchange.com/a/40949


Deterministic wallets employ a concept called a gap limit or "lookahead". Think of the gap limit as the number of unused addresses (as in no transactions on the blockchain) from the index of the last used address that the wallet keeps watching. So for example in electrum the gap limit is 20. Other wallets have more or less. If you have a large block of unused addresses and that block is larger than your gap limit then it's quite possible that multibit won't look for transactions there. Then you have to manually instruct multibit to increase its gap limit. You can do this in electrum so I'm sure there is a way to tell multibit to do the same.


What you can do is have a split setup where you have an offline wallet with the secret seed and an online wallet that only contains the public keys i.e. a watch-only wallet. You create transactions on the online wallet, sneakernet it to the offline wallet for signing and then back to the online wallet to broadcast it. Armory and electrum support this sort of "cold storage" setup.

I can think of a few things that could cause this:

- Last I tried bitcoin core you had to manually shut it down before you shut down the computer i.e. it would not automatically shut down with the OS. If you didn't do this there would be DB corruption
- Like achow101 said DB corruption can be a sign of a hardware problem. In my experience it can be a sign of a failing hard drive.

If I was you I'd definitely make sure bitcoin core was shutting down correctly when you shut down your OS. If you live in an area with power cuts you have to get a UPS or this DB corruption will keep happening.

As for the second point you can run chkdsk to check your hard drive for bad sectors.

BTW electrum is one of the most widely used wallets. You shouldn't be afraid to use it.

creating a new wallet and sending bitcoins there would be the simplest way. it would mean that your addresses would change. you can create a new wallet using file > new/restore.

requests don't expire btw. that part of the interface needs some rewording. suffice it to the address you got from the receive tab will continue to work forever and you should have no problems receiving money to it now and in future.

as for the confirmations issue don't worry either the two transactions will confirm or they won't. you won't lose money. just wait it out.

I believe the library that bitcoin payments for woocommerce uses is faster than the bitwasp ones. I use it for my bitcoin address plugin too. You can grab it from either plugin.

In my plugin you'll find it in includes/libs. The ElectrumHelper file contains the static function mpk_to_bc_address that you can use.

The downside is that this is only for electrum. You'll have to modify it to use another address derivation.

you need a lot more than a word or two to brute force the seed. there are way too many possibilities.

brute forcing only works if you have *some* idea what the password is. otherwise it's a crapshoot.

In the case of p2sh addresses the address is a hash of a script not the hash of a public key. So what are you trying to achieve again?

Go to wallet menu > seed. Tell us what happens when you do this.

I think we missed an opportunity here to get some debug data and maybe file a bug report. I guess next time then..

When this happened in the past we would tell people to delete the files "blockchain_header" and "config" from the electrum data directory. The electrum data directory is one level up from the wallet directory which is located at:

http://docs.electrum.org/en/latest/faq.html#where-is-my-wallet-file-located

So try the above and if it works please do post here so we know this still works!

Every single user. However, most don't report bugs (this is the case with all software). The ones that do help improve the software because they bring those bugs to the devs' attention and then they can fix it.

One difference between 2.7 and older versions when it comes to seeds is that in 2.7 they have standardized seed mnemonics to 12 words for all wallet types. In 2.6 it was 13 words for normal wallets and more words for other wallet types. That doesn't make the 2.6.x seeds any more or less safe though.

The other difference is that the wallet file format changed in 2.7.x. So when you install 2.7.x it upgrades your wallets to the new file format. So old wallets can be used in 2.7.x but newer ones can't be used in 2.6.x.

So you can continue to create wallets in 2.6.x if you prefer but I don't recommend it. I suggest creating new wallets using 2.7.x. The release of lots of point versions in the 2.7.x line should not be taken as a bad thing. If anything it shows that the developers' are actively fixing bugs and improving the software and right now at .11 it's pretty mature.

what is the name of the file and where is it located on your hard drive? take a look at the link below to see the location of electrum wallet files:

http://docs.electrum.org/en/latest/faq.html#where-is-my-wallet-file-located

the wallet file contains json which is a human readable data storage format. it wouldn't be binary code like you've pasted above.

You can save a copy of the wallet file using file menu > copy. Assuming you already have a password set in your electrum wallet then you can upload that file to your cloud account and you are done. When you set a password electrum encrypts the seed using that password. So there is no need to use another encryption app.

You seem to have MBs and GBs confused which is very out of character. I'm guessing they are typos. Might want to correct them.


Bitcoin was designed with the advancement of technology in mind. The whole difficulty adjustment thing is to ensure that, even as CPUs get faster, we continue to get blocks that are 10 minutes apart on average. If you feel that expecting technology to continue to advance is wrong then you should find some other hobby. Forget about bitcoin.