Author

Topic: Multibit and using single addresses from cold storage (Read 750 times)

jr. member
Activity: 56
Merit: 42
OK - I will, thank you.

My strategy will be to backup a multibit wallet with a single address and always import that and close any other wallet before I import my cold stored addresses. This way I'll have access to any change which goes to the other address in the wallet. As long as multibit doesn't create a new address to hold change that is..
hero member
Activity: 778
Merit: 531
If there is more than one address in a wallet, MultiBit will send change to the second address.
Looks like it's made for your purpose.

But don't trust me. Test it.
jr. member
Activity: 56
Merit: 42
I've created some addresses for storage - to be kept in encryped backup offline. They are in the format of the private key strings exported from multibit (a .key file). And I've now split them into individual files with one key in each. So there are a few xxxx.key files with the private keys which I can import into multibit when I need to move bitcoin from an address. I did this because multibit doesn't seem to allow sending or viewing the balance at the level of an individual address.

I understand that there is another address associated when installed - created with the new default wallet. So my question is: when I send the coin from that single imported address, will multibit put change into another address - which to that point I haven't backed up?

If so - what is the best way to use multibit to load cold individual storage addresses and transact with them?

I suppose I could just backup wallets for a similar purpose - but I like the security of human readable keys as the most portable format which I could potentially use with other clients later if necessary.

Thanks for any advice!
Jump to: