problem with multibit

[TookDk]

I am happy you have recovered your bitcoin.
First time I saw a unspend output I was also a little "confused".

[1715054145]

1715054145

[1715054145]

1715054145

[1715054145]

1715054145

[shorena]

-snip-
ahaha thanks man I found it. it was in appdata\roaming\multibit

post your BTC addy i'll send ya 20 bucks

you are welcome

multibit is pretty good at doing extra backups

1MpNbGQrignRG9QKGbEQpz5uCg8KBJrQ9a

[spiceminer15]

sent

[f3tus]

and 0.25441361 BTC goes to 1R8iEGbocHrpq4WNYXTAMcBLCq8rMLB3G which is an address multibit made exactly for that reason.

I'm pretty sure Multibit doesn't work like Bitcoin Core and doesn't generate any new addresses for the change... Blockchain.info doesn't either. I'm guessing spiceminer15 generated it himself sometime.

[shorena]

and 0.25441361 BTC goes to 1R8iEGbocHrpq4WNYXTAMcBLCq8rMLB3G which is an address multibit made exactly for that reason.

I'm pretty sure Multibit doesn't work like Bitcoin Core and doesn't generate any new addresses for the change... Blockchain.info doesn't either. I'm guessing spiceminer15 generated it himself sometime.

Yeah I read up on that a bit to learn how exactly Multibit handles change, only found an old thread from 2013 stating that Multibit either uses the 2nd generated address or (if that does not exist) the only available address. But since the info is so old I posted a more general statement

I was not able to find in the source how Multibit exactly handles change currently. They use "change" a lot A statement here [1] suggests that multibit uses or will use (when HD is live) a new address for change.

sent

confirmed, very generous, thanks


[1] https://github.com/jim618/multibit/issues/139#issuecomment-18482927

[Gws24]

I've been using multibit for about a year now and basically it handles change as follows:

1) you generated only one address in your wallet: the change is sent back to the same sending address.
2) you generated a second address in your wallet: the change is sent to the second address* (bitcoin core would in this case generate a change address automatically)

* This is how it works if the second address has never been used before. If there however is also a balance (input) on the second one multibit might choose to send it from that address and the change back to the first generated address. If both addresses have multiple inputs it might decide to include inputs from both addresses and the change back to either one. For the last case I don't know the rules multibit follows but it probably has something to do with input age and size in order to determine to which address the change gets send to.