i had my private keys on paper, it worked for me OK for a long time so spending become a routine
open multibit classic, create new wallet on ramdisk, export keys, edit file entering my private key,
import keys, send btc, close wallet, delete wallet from ramdisk
i never had a problem with this scenario so i didn't even check if the change came back last couple of times
and last time (the day that my son was born - i have been a bit busy that day
) it didn't came back where i expected, but i only found out today
it happened due to fact that
and due to recent slight rise in prices i was collecting unspent bits from here and there, imported few keys, transferred few times etc.
for some reason i presumed that change will be always given back to sending address (that was the very reason i choose multibit over regular client back in the days that you could count wallets on fingers of one hand)...
i know that i have only myself to blame, but for f**k sake...
open multibit classic, create new wallet on ramdisk, export keys, edit file entering my private key,
import keys, send btc, close wallet, delete wallet from ramdisk
i never had a problem with this scenario so i didn't even check if the change came back last couple of times
and last time (the day that my son was born - i have been a bit busy that day
) it didn't came back where i expected, but i only found out todayit happened due to fact that
Quote
"When additional private keys are created or imported the second address in the wallet is always used for change."
Code:
source: https://github.com/bitcoin-solutions/multibit/issues/661
and due to recent slight rise in prices i was collecting unspent bits from here and there, imported few keys, transferred few times etc.
for some reason i presumed that change will be always given back to sending address (that was the very reason i choose multibit over regular client back in the days that you could count wallets on fingers of one hand)...
i know that i have only myself to blame, but for f**k sake...