If you print the wallet you should extract the private keys and print those. They are pretty small (as EricJ says, 32 bytes a piece) so you print it as 1 line/key, or a sheet full of QR codes.
Please don't print the binary database file entirely, it also contains unrelated info (such as configuration) and index structures/padding for efficiency that you don't need on paper.
Topic: Minimal wallet file size? (Read 2458 times)
With bitcoin -poolsize=0 you'll get 32kb wallet (see https://bitcointools.appspot.com).
I would be interested btw. in the opposite:
What's the maximum wallet size (if there is one), how many privkeys + adresses can you store in a (for example) 1 TB wallet approximately, how hard are the performance hits of huge (multi GB/TB) wallet.dat files and when would they occur (at every block that is received?)?
What's the maximum wallet size (if there is one), how many privkeys + adresses can you store in a (for example) 1 TB wallet approximately, how hard are the performance hits of huge (multi GB/TB) wallet.dat files and when would they occur (at every block that is received?)?
This is a great reason for deterministic key generation.
For a single address offline wallet, you can just generate a private key and record it. This takes only 32 bytes (64 digits in hex, 44 in padded Base64) and is short enough to be stored in a QR code or even written down by hand. People already use this for offline savings. Casascius sells paper wallets containing nine addresses and their private keys on one sheet of paper. BitBills are similar and store the keys in QR codes.
It seems that a fresh wallet.dat is around 140kB, but AFAIK it contains already 100 keys. In order to secure an offline wallet, I see two very distinct threats:
1- getting the wallet stolen
2- losing the wallet
The easiest way to address No1 is to bring the wallet offline. Yet, suddenly, it becomes a lot harder to end-up with super-durable storage.
At 140kB, printing the wallet is rather cumbersome, but assuming that it could be brought down to 1.4kB (with only 1 key), it would be much easier to backup, possibly through super-naive Base64 encoding combined with plain text print (and OCR for recovery, with the option of doing it the manual way if OCR fails for whatever reason).
Are my numbers correct? Any thoughts in providing such an option to produce such thin wallets for the sole purpose of offline saving?
Best regards,
Joannes Vermorel
1- getting the wallet stolen
2- losing the wallet
The easiest way to address No1 is to bring the wallet offline. Yet, suddenly, it becomes a lot harder to end-up with super-durable storage.
At 140kB, printing the wallet is rather cumbersome, but assuming that it could be brought down to 1.4kB (with only 1 key), it would be much easier to backup, possibly through super-naive Base64 encoding combined with plain text print (and OCR for recovery, with the option of doing it the manual way if OCR fails for whatever reason).
Are my numbers correct? Any thoughts in providing such an option to produce such thin wallets for the sole purpose of offline saving?
Best regards,
Joannes Vermorel
Jump to: