I only got the problem if i delete the previous map of Multibit(c:/Program files/Multibit 0.5.14/).With the update i got Multibit 0.5.14 and 0.5.15 in program files, but i don't think u need to keep every map of the previous version in order to run it. Else i need to backup 0.5.14,0.5.15,0.5.16,... if u understand..

@lunarboyYes - that would be nice !At the moment it is bitcoind which is the 'gatekeeper' for the transaction fees (it will become more flexible in the future).The MultiBit fees are as low as you can go currently so I cannot reduce it safely at the moment.

I think the recent run up of the price of bitcoin has surprised everyone but I am sure it will get sorted.

@lunarboyYes - that would be nice !At the moment it is bitcoind which is the 'gatekeeper' for the transaction fees (it will become more flexible in the future).The MultiBit fees are as low as you can go currently so I cannot reduce it safely at the moment.

I think the recent run up of the price of bitcoin has surprised everyone but I am sure it will get sorted.

Thanks for the quick response keep up the fantastic work.

As your online I'll pop in another feature request. would really love to see copy/paste functionality added to the sign message tab (manually typing out addresses and sigs is an accident waiting to happen) I'm too careless :-(

I found an old wallet.dat and imported it into Multibit and to my suprise it showed a balance of 35,000$. Yay! But I could not send the coins. The transaction gets confirmed by one peer only. And after resetting the blockchain my balance is 0$. Do'h! Soo..There is no way that I am rich actually? Just a glitch in the balance display?

You get that if some of the transactions don't accurately match what is on the blockchain (for whatever reason).If you do a 'Tools ! Reset blockchain and transactions' from the day before the first transaction it will go to a Bitcoin node and recreate everything.Can't promise you'll end up with $35k though. :-)

i have same problem. I have 2 computers. yesterday I was transferred my 3.14 BTC from one to another. after that, I sent 50$ BTC to my friend.But multibit showed something spendable BTC! I've been trying to"Reset blockchain and transactions" since yesterday but nothing change!I experienced the same problem before, i lost 1 BTC 1 months ago! http://i41.tinypic.com/2r2vzu1.pnghttp://i39.tinypic.com/2zsa9gj.png

This is almost certainly that the wallets have different private keys/ addresses in them.It is very easy to get two wallets out of sync so I don't recommend having the same wallet on two different computers.With the current random key addresses it is just too confusing.

6. The wallet looks through the new blocks' transactions and stores (in the wallet) the transactions that either send it bitcoin or that confirm its previous spends.

7. MultiBit stores the headers only of the new blocks into its local copy of the blockchain, It does not store the transactions themselves. This is the main reason the MultiBit blockchain is so much smaller than the bitcoind blockchain.

a) That local copy of the (headers only) blockchain is the multibit.spvchain file?

b) If i 'm getting this right the only case that multibit.spvchain updates is when someone sends me coins or when i send some right?

c) Is b. the problem why we can't see the number of confirmations for each transaction?

Also a question mostly about bitcoinj but i think the issue applies to multibit as well

From bitcoinj's wiki

Code:

The Wallet code doesn't scale, at all. All transactions that were ever relevant to the wallet are loaded into memory, all the time, and re-written every time the wallet is saved. This results in a simple on-disk format accessible to many kinds of apps, but has poor performance for heavy users. Also, even if spent transactions are removed, the algorithms used for selecting coins and working with unspent transactions have quadratic time complexity or worse. In time we'll probably switch to a log structured wallet file format to solve this.

What does this mean? That every time the multibit.spvchain is loaded in the memory?

I am suddenly experiencing extreme problems with MultiBit freezing while causing extreme Disk-IO for at least a minute until it becomes responsible again.

* Open MultiBit and wait: after 20 seconds or so it will start showing high disk-IO for one minute.* Open MultiBit and immediately close it again: writes "saving walllet" to title bar and is frozen for a whole minute before it closes.* Open MultiBit, click send and then click new: frozen for 1 minute with high disk io. Enter address and amount, click send: frozen for another minute, enter wallet password: frozen for another minute. First confirmation arrives: frozen for another minute.

I previously had this wallet on my old ThinkPad Pentium-M, 1.3GHz with 500MB RAM and extremely slow HDD (and btrfs!) without any problems. Now I have a 6 core AMD machine 6*3.5GHz and SATA3 HDD (ext4), running Kubuntu 12.04, completely fresh install, only 5 days old, installed latest MultiBit, opened same wallet file and these problems began. I already tried resetting the block chain (this went astonishingly fast compared to my old Laptop) but its still showing these symptoms. I tried to preload libeatmydata.so to disable fsync() but it makes no difference.

What could be causing this? It became essentially unusable. How can I help debugging or solving this problem?