Pages:
Author

Topic: Bug update: Incoming transactions not appearing in MultiBit - page 2. (Read 8593 times)

legendary
Activity: 1708
Merit: 1066
Hi Neverest,

You need your private keys to be able to spend your bitcoin. These are contained in both the '.wallet' file and the private key export. I suggest you do both as that is like wearing a belt AND braces. It takes a few seconds to do and could save you thousands of dollars.

Currently the private key export can be encrypted but you are correct the wallets in the live code are not. There is test code with encrypted wallet support that hopefully is only a couple of weeks away from being released. It is being tested at the moment.
newbie
Activity: 70
Merit: 0
To backup your wallet:

1) Shut down MultiBit so that it writes everything out.
2) Copy the ".wallet" file (MOST IMPORTANT), the ".info" (has labelling info) to a directory on your USB drive.

Also this help tells you how to back up your private keys into a separate file.
https://multibit.org/help_backupWalletUsingPrivateKeys.html

I do both.


Do you need to do both in order to restore your wallet? Or are both actions doing the same thing?
If so, then more files available for trojans etc to send out might be dangerous? Which option is more secure or is it the same?

When exporting the private keys, I can at least encrypt them, but the wallet file seems open?

Thanks
sr. member
Activity: 297
Merit: 250
Don't forget to encrypt the files with at least 20 character password (I use TrueCrypt for that task) to ensure that when you lose USB drive or someone else gets access to your PC he/she won't be able to get access to your money kept in those files.
legendary
Activity: 1708
Merit: 1066
@shkiser
The wallets are stored in a user data area separate to where MultiBit installs itself (if you have used all the defaults in the installer). You can just install the new version.

If you have 20 bitcoins in your wallet but don't have the wallet file backed up somewhere safe (I put mine on two USB drives) then now is a great time to do it !

To backup your wallet:

1) Shut down MultiBit so that it writes everything out.
2) Copy the ".wallet" file (MOST IMPORTANT), the ".info" (has labelling info) to a directory on your USB drive.

Also this help tells you how to back up your private keys into a separate file.
https://multibit.org/help_backupWalletUsingPrivateKeys.html

I do both.
sr. member
Activity: 350
Merit: 250
So if I go and dl the new multibit version is it just a patch and will update my earlier version? Or do I have to install and uninstall the old version.  Will I have a new wallet number? Sorry just want to verify a few things before updating. I have about 20 bitcoins in my wallet and would be bummed if I lost them.
sr. member
Activity: 297
Merit: 250
I'm using 0.4.9 version of Multibit for Linux - should I uprade to avoid problems with this bug?

The other thing I just noticed - Multibit shows 227942 number of blocks when Blockchain.info shows over 228.000. Is this correct or something is wrong here?




EDIT: I switched to version 0.4.23 and now everything looks fine. Version 0.4.9 seems to be some old beta and probably hence the problem.
legendary
Activity: 1708
Merit: 1066
@shkiser. Also I forgot to mention that there is a fix for those incoming transactions not appearing in the latest download on multibit.org.
sr. member
Activity: 350
Merit: 250
all fixed. Thanks
legendary
Activity: 1708
Merit: 1066
If you are connected to a node with bloom filters 53,000 blocks should not take too long. Ten or fifteen minutes. It's easiest just to let it finish syncing. If you do 'View | Messages' you get info as it syncs.
sr. member
Activity: 350
Merit: 250
Fuck I thought I was resetting back to the previous day but just noticed the year was defaulted at 2012.. Its downloading 53,140 blockS! Is there anyway to stop this and redo it? Without fucking anything up? Need help!
sr. member
Activity: 350
Merit: 250
I just followed your workaround information, I hope this helps and I dont lose all of my bitcoins! My balance went to zero, and it now says its syncing with network, but doesnt seem to be doing anything.
sr. member
Activity: 350
Merit: 250
I just had this happen. Transferred nearly 3 btc to my wallet and theyre not showing up at all. Double checked and rechecked and I def didnt mistype the address.. Should I update my client as I havent done this yet bc I didnt want to run into any problems with my balance. What can I do here?
legendary
Activity: 1708
Merit: 1066
If you don't see all the incoming transactions (especially spends if you have your private keys somewhere else too) that can cause subsequent problems.

That's why I am focusing in this bug first. (I have put some extra logging into the code related to other things too mind).
sr. member
Activity: 350
Merit: 250
I had issues with btc being sent out from multibit client. Havent had an issue with incoming transfers tho. Im not sure if this was related. I havent updated my app since early winter of 2012.
legendary
Activity: 1708
Merit: 1066
Hello All,

There have been a few reports recently of transactions being sent to MultiBit and them not appearing.
I thought I would give an update on this bug as it is both serious and annoying.

Symptoms
You send a transaction to MultiBit and it does not appear either as a zero confirmation transaction and does not appear when the next block arrives either.

Workaround
If you do a 'Tools | Reset blockchain and transactions' from before the date of the transaction (I normally choose the day before) the transaction appears.

Tracking it down
I had a user send me some logs last night where this bug occurred - it was a fresh install of MultiBit and he gave me all the details. The current level of logging in MultiBit focuses mainly on the 'top level' activity. Transactions coming and going mainly. There was no sign of the transaction coming in.

I have thus widened the logging to include all the 'low level' activity - this is all the network traffic and all the Bitcoin protocol messages - and this will appear in the next release. The next release will be in a couple of days. This makes the log files a lot bigger and more difficult to read but it needs doing so that we can track this bug down.

Pages:
Jump to: