Quote from: Sampey on February 26, 2017, 02:40:04 PM

Hi,
problem is simple, there are some transactions in my wallet that are badly stored. Result is that anytime i restart the application, a new full synchronization is launched.
This takes at least 1 hours of time, it's not affordable.

If i read the multibit.log file i find these error lines :

Code:

15:10:29.057 [Timer-4] DEBUG o.m.model.exchange.ConnectHttps - checkServerTrusted authType = ECDHE_RSA
[color=red]com.google.bitcoin.store.UnreadableWalletException: Transaction did not deserialize completely: 8eeb1a43fe2c70f026d63a3cc7104551b55cd10d0cd016b057c931a18f050136 vs e046d6416f9ad306d11b1bdfa5c62ea16677e04927514820946b507ccac9c4ca[/color]
at org.multibit.store.MultiBitWalletProtobufSerializer.readTransaction(MultiBitWalletProtobufSerializer.java:624)
at org.multibit.store.MultiBitWalletProtobufSerializer.readWallet(MultiBitWalletProtobufSerializer.java:460)
at org.multibit.store.MultiBitWalletProtobufSerializer.readWallet(MultiBitWalletProtobufSerializer.java:392)
at com.google.bitcoin.core.Wallet.loadFromFileStream(Wallet.java:572)
at org.multibit.file.FileHandler.loadFromFile(FileHandler.java:115)
at org.multibit.network.MultiBitService.addWalletFromFilename(MultiBitService.java:410)
at org.multibit.controller.bitcoin.BitcoinController.addWalletFromFilename(BitcoinController.java:137)
at org.multibit.MultiBit.main(MultiBit.java:433)
at org.multibit.MultiBitInExecutableJar.main(MultiBitInExecutableJar.java:98)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.exe4j.runtime.LauncherEngine.launch(Unknown Source)
at com.exe4j.runtime.WinLauncher.main(Unknown Source)
at com.install4j.runtime.launcher.WinLauncher.main(Unknown Source)
15:10:29.150 [main] ERROR org.multibit.file.FileHandler - com.google.bitcoin.store.UnreadableWalletException Transaction did not deserialize completely: 8eeb1a43fe2c70f026d63a3cc7104551b55cd10d0cd016b057c931a18f050136 vs e046d6416f9ad306d11b1bdfa5c62ea16677e04927514820946b507ccac9c4ca
15:10:29.150 [main] DEBUG org.multibit.file.BackupManager - For wallet 'D:\000-CC\A - Wallet\MultiBit519_Fresh\multibit.wallet' the rolling backup file was 'D:\000-CC\A - Wallet\MultiBit519_Fresh\multibit-data\rolling-backup\multibit-20170226144700.wallet' and the best encrypted/ unencrypted backup was 'D:\000-CC\A - Wallet\MultiBit519_Fresh\multibit-data\wallet-backup\multibit-20170226050635.wallet'
com.google.bitcoin.store.UnreadableWalletException: Transaction did not deserialize completely: 8eeb1a43fe2c70f026d63a3cc7104551b55cd10d0cd016b057c931a18f050136 vs e046d6416f9ad306d11b1bdfa5c62ea16677e04927514820946b507ccac9c4ca
at org.multibit.store.MultiBitWalletProtobufSerializer.readTransaction(MultiBitWalletProtobufSerializer.java:624)
at org.multibit.store.MultiBitWalletProtobufSerializer.readWallet(MultiBitWalletProtobufSerializer.java:460)
at org.multibit.store.MultiBitWalletProtobufSerializer.readWallet(MultiBitWalletProtobufSerializer.java:392)
at com.google.bitcoin.core.Wallet.loadFromFileStream(Wallet.java:572)
at org.multibit.file.FileHandler.loadFromFile(FileHandler.java:149)
at org.multibit.network.MultiBitService.addWalletFromFilename(MultiBitService.java:410)
at org.multibit.controller.bitcoin.BitcoinController.addWalletFromFilename(BitcoinController.java:137)
at org.multibit.MultiBit.main(MultiBit.java:433)
at org.multibit.MultiBitInExecutableJar.main(MultiBitInExecutableJar.java:98)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.exe4j.runtime.LauncherEngine.launch(Unknown Source)
at com.exe4j.runtime.WinLauncher.main(Unknown Source)
at com.install4j.runtime.launcher.WinLauncher.main(Unknown Source)
[color=red]15:10:29.150 [main] ERROR org.multibit.file.FileHandler - com.google.bitcoin.store.UnreadableWalletException Transaction did not deserialize completely: 8eeb1a43fe2c70f026d63a3cc7104551b55cd10d0cd016b057c931a18f050136 vs e046d6416f9ad306d11b1bdfa5c62ea16677e04927514820946b507ccac9c4ca[/color]

Then resynch starts.
This is an infinite loop i can't stop.
I've tried many combinations. I've also tried to export the private key and import the key in a new wallet of a fresh installation. No solution.

Can you help me? I'm going to renonce and change wallet.....but i like multibit so this will be a sad decision for me Undecided

Thanks

I've got the same problem since two days. I used Multibit Classic since 2014 and I was satisfied with it until this.. :/
When I start my wallet it is out of sync. However it worsks well if I wait until it resyncs, and I don't close it. If I restart the wallet, its out of sync again :S

Yesterday I decided to change it to Multibit HD, but I ran into a problem. I installed it, made the secret word and the password too.
After I quit Multibit HD the first time, and tried to re-login, it said the password is not good. However I'm absolutely sure I know my password, as I have made screenshot of it when I set it the first time.
When I choose "I forgot my password" it asks for secret words, I enter them and it accepts it, but it shows "working on password recovery" or something like this, but thats all... I can't reset my password.

So I'm also thinking on choosing a new wallet. I was thinking on Bitcoin Core, but thats big and slow. Never tried electrum so far, but maybe I will give it a chance now.

Btw I hate changes, I don't need fancy shiny shit, I just need a stable, fast and secure something with the very basic functions.
I would have been happy using Multibit Classic for decades, so I'm now a bit disappointed :/

ShodanEnkidu

Posts

Merits