Quote from: gene on June 16, 2011, 05:51:25 PM

Quote from: ShadowOfHarbringer on June 15, 2011, 03:33:07 PM

Quote from: gene on June 15, 2011, 03:21:23 PM

This is the dumbest bullshit ever.

Of course it is, because you said so.
How can we ever doubt you, you are such a SMART-ASS !

Quote from: gene on June 15, 2011, 03:21:23 PM

Everybody please ignore this "advice."

Yes, and become easy prey to hackers of all sorts.

The way to secure a wallet isn't by your laughable Rube Goldberg machine.

Generate a wallet on a dedicated airgapped machine, write down some of its addresses, encrypt the wallet and back up the encrypted file. Then send BTC to the addresses.

See how that works? Now you have a bank from which you can make withdrawals to smaller wallets. Use your brain to figure out how.

Christ. How hard can this be?

It's amateur hour at forum.bitcoin.org...

Since a wallet file is really just a collection of private keys, it seems as though keeping a text file with a collection of private key/address pairs would make just as much sense, if not more sense, than a wallet.dat file itself. Send varying amounts of BTC to each address, and keep track of the addresses on another computer so you can check them for balances in blockexplorer. Then, once PK importing is implemented into the client, you can simply import the private key relating to the address that you wish to "withdraw" from your savings wallet. That way, your wallet file never has to touch the outside world, even to withdraw. The most you ever risk is the amount related to a particular savings address, which can be limited or spread across more or less addresses based on how paranoid you are.