I think this happen because you don't have enough space on your disk and multibit can't sync correctly.
But with the actually fees (250 sat/byte) probably will become impossible address a payment.
There is a 50k satoshi as maximum fees!
Topic: Multibit resyncing everything each time (Read 464 times)
Multibit was abandoned by its developer quite some time ago so it is no longer maintained. You should move to electrum wallet. You can import your private keys from multibit into electrum direct so there is no need for a new address or wallet file transfer.
Great suggestion. I'll try that now.
I have answered here: https://bitcointalksearch.org/topic/m.19071417
Thanks a lot!
Multibit was abandoned by its developer quite some time ago so it is no longer maintained. You should move to electrum wallet. You can import your private keys from multibit into electrum direct so there is no need for a new address or wallet file transfer.
Multibit resyncing everything each time - and 2 other issues
Problem: Multibit had to resync everything from the beginning. Only in the past few days - but each time I opened it!
Syncing several years is a pain.
My workaround was to send all funds to a new wallet, which starts only in 2017 - and thus syncing is super fast again now.
But if for some reason money comes into older addresses - how would I notice that? Not at all then. And those are MANY old addresses.
Now I have finally also checked the "Messages" tab - and found this peculiar message:
The wallet "C:\path\name.wallet" could not be loaded.
Loading the backup wallet
"C:\path\name-data\wallet-backup\name-20170503035735.wallet"
instead.
Isn't that automatism problematic?
What if I had made changes after that auto-loaded backup?
Would't it be better if the walletclient software warned me VISIBLY about such events of a broken file, instead of silently trying to fix them?
I still don't know why that file could not be loaded (RAM issue perhaps? I was operating at the edge of what my machine can do, and with swap switched off)
- and I have bought a hardware wallet now anyways, so multibit will become less important for me now - but I thought, that I better report this issue.
Thanks for the work you put into this beautiful piece of software. It has been such a reliable tool throughout all those years.
Thanks. and: All the best.
---
P.S.: Now "shutting down ..." seems to have a new problem. It is taking ages.
Process manager says:
25 CPU, Memory 99,832K working set and 84,840K Private working set, and 502 handles, and 30 threads.
It's been saying that for minutes now, without change. Only massive CPU usage, but no other value is changing.
Wait? Kill it?
Is this a known problem? Thanks.
P.P.S.: I have killed & restarted. Seems to work still. But I don't like such hard action.
---
another issue:
2 of my transactions were stuck. [good news: they are confirmed now. More than 50 hours later.]
Stuck probably only because I had underestimated the KB size of a tx with almost 10 inputs.
Those two stuck transactions had fees of over 40 sat/Byte and a bit less than 100 sat/Byte.
PLEASE make the fee-slider in Multibit MUCH MUCH longer.
Transaction fee (BTC per KB) 0.00050000 ... is by far not enough.
Also please answer to this thread: https://bitcointalksearch.org/topic/fee-slider-please-extend-range-1841089 where that issue has been discussed for a while.
To change this one number will probably take you only a few minutes, to release a whole new version only a bit longer I guess. But please do that now.
The fee problem in Bitcoin is becoming a moving target - perhaps you want to consider to allow to set the max fee from some config file. Then you do not need to recompile again, once our precious Bitcoin transactions start to cost 2 ... 5 ... 10 ... 20 USD per transaction.
Thanks a lot.
Problem: Multibit had to resync everything from the beginning. Only in the past few days - but each time I opened it!
Syncing several years is a pain.
My workaround was to send all funds to a new wallet, which starts only in 2017 - and thus syncing is super fast again now.
But if for some reason money comes into older addresses - how would I notice that? Not at all then. And those are MANY old addresses.
Now I have finally also checked the "Messages" tab - and found this peculiar message:
The wallet "C:\path\name.wallet" could not be loaded.
Loading the backup wallet
"C:\path\name-data\wallet-backup\name-20170503035735.wallet"
instead.
Isn't that automatism problematic?
What if I had made changes after that auto-loaded backup?
Would't it be better if the walletclient software warned me VISIBLY about such events of a broken file, instead of silently trying to fix them?
I still don't know why that file could not be loaded (RAM issue perhaps? I was operating at the edge of what my machine can do, and with swap switched off)
- and I have bought a hardware wallet now anyways, so multibit will become less important for me now - but I thought, that I better report this issue.
Thanks for the work you put into this beautiful piece of software. It has been such a reliable tool throughout all those years.
Thanks. and: All the best.
---
P.S.: Now "shutting down ..." seems to have a new problem. It is taking ages.
Process manager says:
25 CPU, Memory 99,832K working set and 84,840K Private working set, and 502 handles, and 30 threads.
It's been saying that for minutes now, without change. Only massive CPU usage, but no other value is changing.
Wait? Kill it?
Is this a known problem? Thanks.
P.P.S.: I have killed & restarted. Seems to work still. But I don't like such hard action.
---
another issue:
2 of my transactions were stuck. [good news: they are confirmed now. More than 50 hours later.]
Stuck probably only because I had underestimated the KB size of a tx with almost 10 inputs.
Those two stuck transactions had fees of over 40 sat/Byte and a bit less than 100 sat/Byte.
PLEASE make the fee-slider in Multibit MUCH MUCH longer.
Transaction fee (BTC per KB) 0.00050000 ... is by far not enough.
Also please answer to this thread: https://bitcointalksearch.org/topic/fee-slider-please-extend-range-1841089 where that issue has been discussed for a while.
To change this one number will probably take you only a few minutes, to release a whole new version only a bit longer I guess. But please do that now.
The fee problem in Bitcoin is becoming a moving target - perhaps you want to consider to allow to set the max fee from some config file. Then you do not need to recompile again, once our precious Bitcoin transactions start to cost 2 ... 5 ... 10 ... 20 USD per transaction.
Thanks a lot.
Jump to: