Tag Archives: bitcoin

I just wanted to ask If it makes sense if I want to print out my wallet.dat to encode it with base64?

I also read that the backup would become useless, if I get any receivements or make deposits and I would have to print out the wallet.dat again?

I would like to encode my wallet.dat with base64, print it and hide it in safe.

when my laptop breaks down and my other backups are also damaged (why every), i could scan my printed wallet.dat with OCR, decode it with base64 and just load it into the normal bitcoin client?

does this sound correct?
or are there any things I’m missing?

I dont want to rely on other software, no other web apps or key/password generators…

I got the address for my account on a site and wrote it down. As I had had a huge hassle buying my bitcoin that morning due to problems with the vendor’s site (and which they denied was at their end for 3 or more hours, nearly drove me spare) I was flusterred quite badly.

Anyway, for some reason that is still not apparent to me I clicked on a button saying “generate new account”. However, as the site kicked me out due to poor connectivity and it flagged me that “your request could not be processed”, I sent the bitcoin off to the address I had written down.

Some hours later I went to the site to check my balance…my funds were not there. There was A NEW ADDRESS for sending bitcoin to in my account details.

So, it would appear that I have sent my bitcoin to a valid address that is now redundant.

What will happen to my bitcoins? Will they bounce around for a few days before coming back or will they just disappear into the ether?

The Bitcoin Protocol-specification gives an example of double-SHA-256 encoding.

hello
2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824 (first round of sha-256)
9595c9df90075148eb06860365df33584b75bff782a510c6cd4883a419833d50 (second round of sha-256)

I’ve tried various SHA256 calculators and the first encoding matches no problem, but the second always resolves to

d7914fe546b684688bb95f4f888a92dfc680603a75f23eb823658031fff766d9

I’ve also tried UPPERCASE and swapping the byte endianness.