Actually, I found a tool now. And sad: MultiBit is declared dead. Long live Multibit.

The tool works in 7 out of 10 cases.

Anyone has any idea how to fix this problem?

https://github.com/drakoin/read-multibit-wallet-file/blob/master/issue-01.md

Hello!
Syncing (several years old) multibit wallets has already taken > 24 hours, then it had some problem, and went back all the way to the beginning. Grrrrr.

Unfortunately, the private key export does not work unless the wallet is fully synced. Bad. Sad. Mad.

So now I am wondering whether I can extract the private keys myself, from the wallet files.
They start with 'org.bitcoin.production...' but the remainder is garbled binary stuff.

Which (open source) library could I use to decompose the multibit.wallet files?
I am good with python.

All wallets are encrypted.

Any pointer - thank you very much.

Enjoy the mooning


----

EDIT: renamed the thread from
    exporting private keys directly from multibit.wallet file? How to? Python tools?
to
    mbexport has some bug - MaxListenersExceededWarning - please help, thanks.

Thanks for your post that you do not have any problems, I am happy for you.
We others however, are in this situation:



That post about the 1,039,183 KB was at 10:13:53 PM

I stopped the insanity at 1,074,848 KB at 2:12 AM

Because that was only 35,665 KB in 4 hours.

If that bootstrap.dat goes into a blk0001.dat that is > 2,000,000 KB large, then this tells me that I would have to wait another

(1,000,000 KB / 35,665 KB) * 4 hours = 112 hours = 5 days

during which (a) my computer has to be on 24/7, (b) the SSD will get unnecessarily f***ed, and (c) my patience will evaporate.



Idea / Solution / Let's try this:

Can anyone please zip, and upload (e.g. mega.co.nz) the    blk0001.dat + /database/ + /txleveldb/    (instead of the bootstrap.dat)?  Or are there any bitcoin-technical reasons which speak against that?

I would really like to revive this wallet, and as you can see in my posts, I am trying hard, but to wait a week for a bootstrap to unravel ... is too much IMHO.

This is insane:

To get blk0001.dat from 1,010,000 to now 1,039,183 ... took all evening. And it has to go over 2,000,0000 KB - right?

At this speed the bootstrap.dat reading would take until the end of the month. Or the end of the summer.



There must be another solution.

thx


so you mean just simple syncing? I am already at 4.04% with that, and on my slower machine, and HD.
 
On the other machine the blk0001.dat is at 1,008,665 KB ... but it has slowed down so much that it needs one second per KB now.
For another 1 million KB that would mean 10^6 / 60 /60 / 24 = 11 days from now
the bootstrap.dat --> blk0001.dat procedure would be ready. Plus my SSD wrecked I guess.

What if someone publishes his blk0001.dat + /database/ + /txleveldb/ (instead of the bootstrap.dat)?  That would save us 12 days, right?

Just wanted to tell that after a couple of restarts ... it is finally syncing fine ... block 91203 ... 2.47% done

Thanks a lot for your quick answer.

Over 2 GB ... So shouldn't I rather go for a newer bootstrap than the 1,851,231 KB one ? 

Who would be willing to do a newer one?



Alright.

After quitting, and restarting, I could now get it to 5372 blocks.
But now it is stuck there.

Plus, it is assuming 3695262 blocks now, not 2.8 million.

quit. restart ... 5872 blocks now, but assuming 2100001 blocks now. This is confusing. Are there bad nodes perhaps, with wrong blocks?


And: Do I have to always kill and restart the wallet, to get it syncing continuously?




Good to know. Is your IP among the list I got from coinexchange?

I am trying to access my old coins, but is turning into a cumbersome experience.

Yes, I am using the newest Mintcoin v2.0.2.0   (MintCoin-Qt.exe)

Two paths, both *sigh*:


1) bootstrap.dat (1,851,231 KB)

the resulting blk0001.dat is 968,000 KB now, but only because I started it already 14 hours ago. So does this really take almost 2 days, even with a bootstrap offline block repository?



2) syncing from scratch, on a 2nd machine.
First there were no peers, but then I added many dozens of them from https://www.coinexchange.io/network/peers/MINT and finally got ... "6 active connections".
But now it is stuck at block 500.  2830755 to go?



About (1) no one can do anything I think. It just needs 2 days of patience - right?

Idea: Is there a MINT light wallet, into which I can import my secret keys, to be able to send my MINT ?


About (2) ... I think you/someone should try to find out what is wrong with your coin:
Please download MintCoin-Qt.exe v2.0.2.0, then move/rename/delete everything in %APPDATA%/MintCoin (apart from your wallet.dat of course)...

... and test it yourself:
MINT v2.0.2 might have an issue with block 500 when syncing from scratch.



Hope this helps,

(-: Mf7wCiDe84QfG9SQgUkwTYxfYvpY2Rooua Thx!

Looks like I was VERY right with the conjecture in this thread.

Great suggestion. I'll try that now.

I have answered here: https://bitcointalk.org/index.php?topic=1841089.msg19071417#msg19071417

Thanks a lot!

Thanks to everyone who is trying to help.


Yes, in the beginning of the "great bitcoin traffic jam of 2017" that still helped. viabtc got my transactions mined, hail to their innovative & only-indirectly-selfish idea. Great that not everyone is myoptic in this culture.

By now ... that service is useless. 100 offered transactions are nothing versus 100k stuck transactions.

And I have added one more transaction to that today, using Multibit again. Wrong I guess. Multibit is broken beyond repair. Not that the software does not work, no it is great still, and I like it - but a fee slider which might have worked well in the early 20th century, can -when stuck within the old limits- sabotage the whole surrounding software. In 2017 it doesn't work anymore. A simple fee slider maximum, one integer -  and a whole software breaks.



Of course, I would like the Bitcoin warmongers on all sides to finally come to some intelligent peace treaty about scaling, and soon. But as long as that doesn't happen:

I actually do not mind to pay higher fees, to transact in the best money system ever invented. But what I do mind is that I cannot choose higher fees, within Multibit.  


Why the author/s not simply publish/es a new version, newer than 0.5.19, is beyond me. I don't think that Multibit is open source, is it? Could someone from the inside perhaps let a USB stick containing the Multibit sourcecode fall from a truck, into the right hands? That would be nice, thank you. Perhaps those right hands can create a version with higher possible fees. Thanks.

EDIT:

Nice, thanks a lot for this suggestion:


Fantastic thanks.


Yes, Microsoft did that too, with XP.

Thanks for your answers. So the 3 of us seem to be of a similar opinion on this.

I have mentioned this issue again now, in this other thread "Multibit resyncing everything each time"

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://bitcointalk.org/index.php?topic=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.

Thanks a lot, yes that sounds easy.

> we already have a coin swap system in place
but the new chain is not running yet - or is it?  So no need to swap anything yet, right?


Congrats to everyone for the price explosion. I had a ladder of sell prices in place - and they ALL got hit.  But the height of this crazy peak was hard to predict. Could have gotten 3 times as much, what a pity.  But any plus is always good, so let's be modest.


Now I am going to try to find my off-exchange coins. I think I have wallet.dat files somewhere ...
... I just download a wallet software, and the blockchain from https://muex.io/Bootstrap and then I sync those wallet.dat files, and send the coins to an exchange - correct?

sorry for the naive questions, but ... busy .... just could not follow this thread.


------
EDIT: Yes yes yes. All good. And I did find some old coins. Nice.

(in multibit classic)

the slider can be set between
0.00001000 and 0.00050000 BTC per KB

If I understand this correctly https://bitcoinfees.21.co/ https://bitcoinfees.github.io/

then it would make sense to allow up to >200.000 Satoshi per KB - right?

That means the slider should go up to 0.00210 - right?

Please add that TODO for a future update, thanks a lot.

Please help me with the above. Thanks.

Please help me with the above. Thanks.

That seems to have helped. Thanks.



Now a new problem:

I am trying to send,
from account "PRIVATE" (where I have a few coins)
to account "PUBLIC"
pay to (a   S.................................   address)



After "Confirm send coins: Are you sure to send ... SDC SHADOW, ring size .., to SDC lalala (S.................................)?".

and Yes button, I get a





ShadowCoin version v 1.5.0.2

That "all" could also mean all 6,641,021 SDC in existence.

So is there a 3.32 million SDC cap - or not?

I am trying that now.

Thanks a lot!