BTC balance mismatch

[Herp-a-derp]

Hi,

First off, great job with the client, it is very good.

I have one small problem, which is probably due to my lack of knowledge. I noticed that my client is showing my balance is around 0.4BTC less than what is shown on blockchain.info, all transactions are fully confirmed.

Is there are way to fully resync the client with the blockchain without losing my wallet?

Thanks.

[Raoul Duke]

Go to Tools -> Reset Blockchain and Transactions and on the calendar choose a date before your first transaction to that wallet and click the button to Reset Blockchain and Transactions.
wait a couple minutes and all will be good.
The above will not touch your wallet file at all and it's safe.

Multibit has that bug, that when you leave it open it sometimes will not see incoming transactions.

[Benson Samuel]

Sorry!, Removed that!

[Herp-a-derp]

Go to Tools -> Reset Blockchain and Transactions and on the calendar choose a date before your first transaction to that wallet and click the button to Reset Blockchain and Transactions.
wait a couple minutes and all will be good.
The above will not touch your wallet file at all and it's safe.

Multibit has that bug, that when you leave it open it sometimes will not see incoming transactions.

Worked perfectly, thanks very much 

[Mike Hearn]

Could you tell me the txid please? It's obviously not supposed to miss transactions like that .... that's a pretty serious bug. Unfortunately without logs it would be hard to debug. Jim, does MultiBit do full logging to a file?

[Raoul Duke]

Could you tell me the txid please? It's obviously not supposed to miss transactions like that .... that's a pretty serious bug. Unfortunately without logs it would be hard to debug. Jim, does MultiBit do full logging to a file?

Here are 2 TX's that only showed up after I Reset Blockchain and Transaction on my own wallet.
0c4131316fd4f07c42e2ca94b1aab2635598ca111851b5917f9124a34731acca
2b6ee934e5a816d68005a7fdf2b45f858599562050bb3cc2d70703cab008b114

Only thing in common they have is that both are a sendmany transaction.
I haven't noticed that detail until now. It may well be the reason.

[jim618]

@Mike
I log all the incoming and outgoing transactions, and all the logging generated by Wallet in particular.
The log files are multibit_debug.log and multibit_console.log in the <MultiBit user data directory>/log dir.
There are daily cuts of the logs.

@Psy
If you zip up the logs you have in the <MultiBit user data directory>/log and mail them to me (see https://multibit.org/team.html) I will have a look.

I only really need the logs for when you sent / received those particular txes but it's probably quicker for you just to zip the whole lot.

[Raoul Duke]

@Mike
I log all the incoming and outgoing transactions, and all the logging generated by Wallet in particular.
The log files are multibit_debug.log and multibit_console.log in the <MultiBit user data directory>/log dir.
There are daily cuts of the logs.

@Psy
If you zip up the logs you have in the <MultiBit user data directory>/log and mail them to me (see https://multibit.org/team.html) I will have a look.

I only really need the logs for when you sent / received those particular txes but it's probably quicker for you just to zip the whole lot.

The thing is, those are incoming transactions, and they only "arrived" after doing the Reset trick. You sure the logs will help in any way?

There are a couple more, but those 2 are the one's I'm sure about. If it helps I can tell you those are Coinurl.com payments. Maybe you can contact mc_lovin here in the forum and ask him how he sent the payments.

Anyway I'll zip up the logs folder and send it to you.

[jim618]

They might help - with the recent fix for the zero confirmation tx there is now a check in the code for tx that are nonfinal.
These don't get added to the wallet but there is still some logging in there. It could be that MultBit is seeing some tx that are non-final (or treated as such) as zero confirmation tx and then only adding them when they appear in a block.

The logs should rule that hypothesis out one way or the other as I can hunt around when those tx appeared.

[Raoul Duke]

OK, mailing the zip to you right away.

[jim618]

Cheers

[jim618]

@Psy - I have been through your logs and - as you surmised - there was nothing to indicate what happened.

I am pretty sure you are right that there is a bug in MultiBit/ bitcoinj that some tx are not appearing in the wallet. Andreas is seeing similar behaviour in his Bitcoin Wallet.

Looking at your specific tx in blockchain.info there does not appear to be anything unusual about them - the scripts are all conventional.

I'm putting in more logging for when the transaction come in.

[Raoul Duke]

Like I said, the only thing those 2 transactions have in common is that they came from the same person(user mc_lovin in the forum) and they're sendmany transactions, being my address only 1 of the several outputs.

I've been avoiding to keep Multibit open all the time because of it. It's not really a problem because Multibit opens and catches up with the blocks very fast. But I miss having the exchange rate right there lol

[jim618]

Yes it is an annoying bug that is for sure.

Oh well - I am sure we will track it down and eliminate it.

[Mike Hearn]

I could take a look too. I'd need to know the addresses you were using to receive those payments.

Jim, do you have the raw/full bitcoinj logs? I'm not sure why you'd only log a subset, that seems like more work than just logging everything ...

[jim618]

I'll mail you the logs.
If you log everything the logs become virtually incomprehensible as even at debug there is a lot of stuff being logged.

edit: done

[Raoul Duke]

I PM'd the address to Mike.

[Mike Hearn]

The default logging level of bitcoinj I find to be good enough. There's usually no such thing as too much logging, as you can always post-process them. That said if logs are flooded with useless data then that's obviously bad, the trick is in the balance.

[jim618]

Yeah - I've widened up the logging - see the 'Bug update' post.