@meebs
From MultiBit version 0.4.23 your change is now sent to the SECOND private key in the wallet - if it exists - rather than the first.
This means that if you create a new wallet and import some keys from 'somewhere', the change will be sent to one of the addresses you just imported.
Also note that if you use the MultiBit "File | Delete Wallet" option it is a secure delete. It overwrites both the wallet and the rolling backup wallet with nonsense data before deleting the file. This is to prevent attackers recovering your wallets at a later date from your disk. By the sounds of it you fortunately did an operating system delete so could recover it.
Topic: Anyone having a problem with multibit? (Read 836 times)
multibit tried to screw me over one time... it randomally sweeped 7btc from one of my blockchain addresses i imported into the local address it created. i didnt realize this until after i deleted the wallet file.
Thankfully Iwas able to recover the file and get my coins back.. this was only a month ago to.. so the thought of losing $350 was a scary one.
Thankfully Iwas able to recover the file and get my coins back.. this was only a month ago to.. so the thought of losing $350 was a scary one.
Ive had coins stuck in limbo for the last 2 hours, still have only been seen by 1 peer, which i assume is myself and hasnt touched the chain yet.Ive had held up for like a half hour before, but those had at least hit the chain and waited for confirmations. Anyone having a similar problem?
edit: sigh.....of course it hits the chain as soon as i hit send, i should have bitched earlier.
edit: sigh.....of course it hits the chain as soon as i hit send, i should have bitched earlier.
Jump to: