Ok so just to be sure.
In i run the bitcoin clien from inside the true crypt flashdrive.. on ANY COMPUTER it will find my... "Account" and have my coins in it?
And I can send money to that wallet at any time like on monday, plug the drive in on friday and it should pick up the coins?
Topic: . - page 5. (Read 64509 times)
Had a quick question,
I did all the true crypt and set up an image. I put all my data/bitcoin folders inside. I made a copy and placed one on my storage drive and one on my flash drive.
I then put my flash drive away. Afterwards I mounted my image from the C:\ drive and received some bit coins.
If my computer crashes do I lose those bit coins? Or can I bring out my flashdrive and it will also receive those coins?
Thanks.
I did all the true crypt and set up an image. I put all my data/bitcoin folders inside. I made a copy and placed one on my storage drive and one on my flash drive.
I then put my flash drive away. Afterwards I mounted my image from the C:\ drive and received some bit coins.
If my computer crashes do I lose those bit coins? Or can I bring out my flashdrive and it will also receive those coins?
Thanks.
the client generates 100 keypairs on setup and saves these in your wallet. whenever you get a new address, it picks a key from this key pool. this includes autogenerated 'my receiving address' AND hidden receiving addresses used to receive change.
If I send you 4btc but my only coin is worth 5btc, 1btc is sent back to me at a new 'change' address.
If it turns out that I've used all 100 of my addresses, that new 'change' address will (AFAIK) be generated on the fly. It will be saved in wallet.dat BUT at this point your original backup is out of date. So, if you actively send coins from a wallet, be aware that after some point your old backups will go out of date.
And in order to restore using the wallet.dat file? I assume you simply replace any wallet.dat(fresh install) with my backup wallet.dat and then I can use the rescan feature to retrieve any transactions that were done previously?
Yep, if it's a new installation you might not even need to use -rescan.
Awesome!
Also, which files can I save to have a "compact" version? I copied all appdata & bit coin folder to my encrypted drive, but I would rather a smaller version I could upload online. Not my main one, but a back up in case I end up losing everything. I probably wouldn't ever update this one unless I needed to replace my main encrypted key that has the block files.
Thanks again.
Also, which files can I save to have a "compact" version? I copied all appdata & bit coin folder to my encrypted drive, but I would rather a smaller version I could upload online. Not my main one, but a back up in case I end up losing everything. I probably wouldn't ever update this one unless I needed to replace my main encrypted key that has the block files.
Thanks again.
If you're only doing it as a backup, you only need to back up one file: wallet.dat
However you should probably encrypt it with something like True Crypt first before uploading online.
Great. I've got True Crypt up and running already. I decided to make a larger encrypted file with the blocks that I'm using on my main PC and a flash drive backup. I'll take the wallet.dat and encrypt it then distribute to a couple of places online.
And in order to restore using the wallet.dat file? I assume you simply replace any wallet.dat(fresh install) with my backup wallet.dat and then I can use the rescan feature to retrieve any transactions that were done previously?
Awesome!
Also, which files can I save to have a "compact" version? I copied all appdata & bit coin folder to my encrypted drive, but I would rather a smaller version I could upload online. Not my main one, but a back up in case I end up losing everything. I probably wouldn't ever update this one unless I needed to replace my main encrypted key that has the block files.
Thanks again.
Also, which files can I save to have a "compact" version? I copied all appdata & bit coin folder to my encrypted drive, but I would rather a smaller version I could upload online. Not my main one, but a back up in case I end up losing everything. I probably wouldn't ever update this one unless I needed to replace my main encrypted key that has the block files.
Thanks again.
If you're only doing it as a backup, you only need to back up one file: wallet.dat
However you should probably encrypt it with something like True Crypt first before uploading online.
Had a quick question,
I did all the true crypt and set up an image. I put all my data/bitcoin folders inside. I made a copy and placed one on my storage drive and one on my flash drive.
I then put my flash drive away. Afterwards I mounted my image from the C:\ drive and received some bit coins.
If my computer crashes do I lose those bit coins? Or can I bring out my flashdrive and it will also receive those coins?
I did all the true crypt and set up an image. I put all my data/bitcoin folders inside. I made a copy and placed one on my storage drive and one on my flash drive.
I then put my flash drive away. Afterwards I mounted my image from the C:\ drive and received some bit coins.
If my computer crashes do I lose those bit coins? Or can I bring out my flashdrive and it will also receive those coins?
quick answer: you loose nothing. the information that you received bitcoins is in the network's shared block chain. the client can anytime start with parameter -rescan and search for all (inc. missed) transactions to verify it's balance
Awesome!
Also, which files can I save to have a "compact" version? I copied all appdata & bit coin folder to my encrypted drive, but I would rather a smaller version I could upload online. Not my main one, but a back up in case I end up losing everything. I probably wouldn't ever update this one unless I needed to replace my main encrypted key that has the block files.
Thanks again.
Had a quick question,
I did all the true crypt and set up an image. I put all my data/bitcoin folders inside. I made a copy and placed one on my storage drive and one on my flash drive.
I then put my flash drive away. Afterwards I mounted my image from the C:\ drive and received some bit coins.
If my computer crashes do I lose those bit coins? Or can I bring out my flashdrive and it will also receive those coins?
Thanks.
I did all the true crypt and set up an image. I put all my data/bitcoin folders inside. I made a copy and placed one on my storage drive and one on my flash drive.
I then put my flash drive away. Afterwards I mounted my image from the C:\ drive and received some bit coins.
If my computer crashes do I lose those bit coins? Or can I bring out my flashdrive and it will also receive those coins?
Thanks.
SpiderOak <--
It's like dropbox except that it's encrypted locally before transmission to their servers so the company only sees ciphertext.
I'd skip all the steps about truecrypt and just use spideroak. If you want to use the email backup method, then 1) schedule jobs to make backups, 2) use whatever encryption capable archiving tool you like, such as bzip2+openssl or in windows 7zip/WinZip etc 3) use a command line emailer mail/sendmail/sendEmail/etc in linux or something like blat in windows, to automatically mail it to your gmail account.
It's like dropbox except that it's encrypted locally before transmission to their servers so the company only sees ciphertext.
I'd skip all the steps about truecrypt and just use spideroak. If you want to use the email backup method, then 1) schedule jobs to make backups, 2) use whatever encryption capable archiving tool you like, such as bzip2+openssl or in windows 7zip/WinZip etc 3) use a command line emailer mail/sendmail/sendEmail/etc in linux or something like blat in windows, to automatically mail it to your gmail account.
it's easy to do this if you can parse wallet.dat yourself. but without doing that, there ought to be a relatively straightforward way to do what you want:
keeping the 'large' wallet off of the public internet, connect a new, private, uncompromised node to it alone and make an ip-address (public key) payment of the smaller amount you want to spend. then disconnect the 'large' wallet's node, connect the recipient's node to the public internet, confirm the receipt, and spend the coins from there.
obviously you can't spend coins without attaching something to the network at some point, but the goal is to segregate your large holdings from the public internet.
if this method is too complicated, you could of course generate arbitrarily many private wallet.dat files and store small amounts in each of them, then move them over one by one. it wouldn't be hard to write better software tools to avoid the need for these steps, though.
keeping the 'large' wallet off of the public internet, connect a new, private, uncompromised node to it alone and make an ip-address (public key) payment of the smaller amount you want to spend. then disconnect the 'large' wallet's node, connect the recipient's node to the public internet, confirm the receipt, and spend the coins from there.
obviously you can't spend coins without attaching something to the network at some point, but the goal is to segregate your large holdings from the public internet.
if this method is too complicated, you could of course generate arbitrarily many private wallet.dat files and store small amounts in each of them, then move them over one by one. it wouldn't be hard to write better software tools to avoid the need for these steps, though.
Well, since it'd be a (long term) savings account, I wouldn't need to actually worry about it for a while, so hopefully when the time came to spend it (maybe 2 or 3 years), there'd be a lot more sophisticated wallet-parsing tools around. So I could split off a few BTC at a time and transfer to a net-connected PC via flash drive.
it's easy to do this if you can parse wallet.dat yourself. but without doing that, there ought to be a relatively straightforward way to do what you want:
keeping the 'large' wallet off of the public internet, connect a new, private, uncompromised node to it alone and make an ip-address (public key) payment of the smaller amount you want to spend. then disconnect the 'large' wallet's node, connect the recipient's node to the public internet, confirm the receipt, and spend the coins from there.
obviously you can't spend coins without attaching something to the network at some point, but the goal is to segregate your large holdings from the public internet.
if this method is too complicated, you could of course generate arbitrarily many private wallet.dat files and store small amounts in each of them, then move them over one by one. it wouldn't be hard to write better software tools to avoid the need for these steps, though.
keeping the 'large' wallet off of the public internet, connect a new, private, uncompromised node to it alone and make an ip-address (public key) payment of the smaller amount you want to spend. then disconnect the 'large' wallet's node, connect the recipient's node to the public internet, confirm the receipt, and spend the coins from there.
obviously you can't spend coins without attaching something to the network at some point, but the goal is to segregate your large holdings from the public internet.
if this method is too complicated, you could of course generate arbitrarily many private wallet.dat files and store small amounts in each of them, then move them over one by one. it wouldn't be hard to write better software tools to avoid the need for these steps, though.
3) If you were extremely wealthy, would you prefer storing your bitcoins in a single address or spread it out evenly over 100 addresses, making it 100 times more likely for a collision to happen but only being able to lose 1% of your wealth at a time?
even if that happened you would not lose any coins, as I understand it.You absolutely could lose coins if a collision occurred. The new 'owner' of the relevant keys could spend your money.
So to John's question, it would simply be a matter of individual preference. Both setups would have the same chance of money being taken via collision, but one is 'all or nothing' while the other is more gradual.
@Vladimir, it's possible to have a savings wallet that has NEVER been online, but how do you securely SPEND from such a wallet?
One very important addition - make sure that the private key is only, ever entered on an "absolutely secure" computer.
I am "reasonable sure" that my home computer is free of keyloggers, but not absolutely sure. I plan to format a new computer, and only use it for bitcoin - this way I'm "almost absolutely sure" it has no keyloggers installed.
Three scenarios that I think of separate "almost absolutely sure" from "absolutely sure":
1. The OS image I'm using contains a hidden keylogger.
2. Bitcoin itself contains a keylogger.
3. My hardware/firmware contain a keylogger.
Out of these, I'd say #1 is the most likely, and if I choose my OS image well, I can reduce that to "not bloody likely" as well.
I am "reasonable sure" that my home computer is free of keyloggers, but not absolutely sure. I plan to format a new computer, and only use it for bitcoin - this way I'm "almost absolutely sure" it has no keyloggers installed.
Three scenarios that I think of separate "almost absolutely sure" from "absolutely sure":
1. The OS image I'm using contains a hidden keylogger.
2. Bitcoin itself contains a keylogger.
3. My hardware/firmware contain a keylogger.
Out of these, I'd say #1 is the most likely, and if I choose my OS image well, I can reduce that to "not bloody likely" as well.
3) If you were extremely wealthy, would you prefer storing your bitcoins in a single address or spread it out evenly over 100 addresses, making it 100 times more likely for a collision to happen but only being able to lose 1% of your wealth at a time?
even if that happened you would not lose any coins, as I understand it. 
Couple of questions:
1) Is TrueCrypt disk encryption superior to encrypting a single file with 7z or something and why do you prefer TrueCrypt above the alternatives?
2) How many characters would you use for the password? I hear that ideally the password should have 128 bits of entropy and that unicode characters have more entropy than ascii, is this true?
3) If you were extremely wealthy, would you prefer storing your bitcoins in a single address or spread it out evenly over 100 addresses, making it 100 times more likely for a collision to happen but only being able to lose 1% of your wealth at a time?
1) Is TrueCrypt disk encryption superior to encrypting a single file with 7z or something and why do you prefer TrueCrypt above the alternatives?
2) How many characters would you use for the password? I hear that ideally the password should have 128 bits of entropy and that unicode characters have more entropy than ascii, is this true?
3) If you were extremely wealthy, would you prefer storing your bitcoins in a single address or spread it out evenly over 100 addresses, making it 100 times more likely for a collision to happen but only being able to lose 1% of your wealth at a time?
Wouldn't you just need to copy the wallet with your savings account once? If you send all the bitcoins you want to keep in savings to that one address, you should always be able to restore it in the future even if you only had the initial copy of the wallet. Am I wrong?
That is true. As long as you don't generate a bunch of new addresses with that wallet and/or send coins with it, you can access all the coins it received with an older backup.
Wouldn't you just need to copy the wallet with your savings account once? If you send all the bitcoins you want to keep in savings to that one address, you should always be able to restore it in the future even if you only had the initial copy of the wallet. Am I wrong?
You should try Wuala.com. ( it also accept Bitcoin as payment: http://www.wuala.com/bitcoin )
It has many features like Dropbox, but it also include a local encryption before the upload
It has many features like Dropbox, but it also include a local encryption before the upload
Sweet..this saves me the extra step of encrypting my wallet.dat before I upload it to Dropbox..hmm..or I can copy the encrypted file to both for extra redundancy :p
Jump to: