I understand, but this would seem like an essential safety fix, and if it could prevent people from losing coins...
Well the best fix is to have a fully deterministic wallet with wallet words that you can use to restore your wallet.
AKA MultiBit HD
Topic: HELP ME! Wallet corrupt? 0,03 BTC for who can fix this issue (Read 3451 times)
Well the best fix is to have a fully deterministic wallet with wallet words that you can use to restore your wallet.
AKA MultiBit HD
I understand, but this would seem like an essential safety fix, and if it could prevent people from losing coins...
+1
I second this. You shouldn't just ditch a variant of your software especially if there is a possible solution to a bug users may encounter. It is far wiser to wrap that up where possible and then move forward.
The council approves this message.
I understand, but this would seem like an essential safety fix, and if it could prevent people from losing coins...
What we plan to do in version 0.1.5 is:
What about MultiBit Classic? Same thing with corrupted files can and did happen there...There is only essential network and safety fixes going into MultiBit Classic now.
Ideally we'd like people to move off Classic and onto HD (or another deterministic wallet if people prefer another client) now.
We cannot actually stop people using Classic but it is 'Bitcoin 2013' era so getting a bit old now.
What we plan to do in version 0.1.5 is:
What about MultiBit Classic? Same thing with corrupted files can and did happen there... @GoldTiger69
We suspect that the root cause is all the mutated tx flying around the network.
We've seen a stack trace that indicates that the password correctly decrypted the wallet file and then when the wallet was deserialised (i.e turned into an object) it wasn't consistent.
Specifically, a transaction has inputs which are the outputs of another, older tx. We've seen instances where this link wasn't valid which is almost certainly due to tx malleability. If the parent tx was the 'transaction that died' in a tx malleability attack you would see this.
What we plan to do in version 0.1.5 is:
+ not allow LowS signatures in the wallet at all.
+ at wallet load, if the wallet is inconsistent automatically perform a Wallet repair, which clears out all the tx and then resyncs.
This should eliminate this class of failure going forward.
We suspect that the root cause is all the mutated tx flying around the network.
We've seen a stack trace that indicates that the password correctly decrypted the wallet file and then when the wallet was deserialised (i.e turned into an object) it wasn't consistent.
Specifically, a transaction has inputs which are the outputs of another, older tx. We've seen instances where this link wasn't valid which is almost certainly due to tx malleability. If the parent tx was the 'transaction that died' in a tx malleability attack you would see this.
What we plan to do in version 0.1.5 is:
+ not allow LowS signatures in the wallet at all.
+ at wallet load, if the wallet is inconsistent automatically perform a Wallet repair, which clears out all the tx and then resyncs.
This should eliminate this class of failure going forward.
Yep, hat makes sense. It should solve the issue of the inconsistent wallet.
Btw, maybe an option for a backup of the rolling and zip directories to a USB would be helpful? I have noticed that not many people trust Cloud places for a backup (I certainly don't, and not because of being hacked; but if they go out of business or simply they become unreachable, then I'll be paying the consequences). Just a tough.
@GoldTiger69
We suspect that the root cause is all the mutated tx flying around the network.
We've seen a stack trace that indicates that the password correctly decrypted the wallet file and then when the wallet was deserialised (i.e turned into an object) it wasn't consistent.
Specifically, a transaction has inputs which are the outputs of another, older tx. We've seen instances where this link wasn't valid which is almost certainly due to tx malleability. If the parent tx was the 'transaction that died' in a tx malleability attack you would see this.
What we plan to do in version 0.1.5 is:
+ not allow LowS signatures in the wallet at all.
+ at wallet load, if the wallet is inconsistent automatically perform a Wallet repair, which clears out all the tx and then resyncs.
This should eliminate this class of failure going forward.
We suspect that the root cause is all the mutated tx flying around the network.
We've seen a stack trace that indicates that the password correctly decrypted the wallet file and then when the wallet was deserialised (i.e turned into an object) it wasn't consistent.
Specifically, a transaction has inputs which are the outputs of another, older tx. We've seen instances where this link wasn't valid which is almost certainly due to tx malleability. If the parent tx was the 'transaction that died' in a tx malleability attack you would see this.
What we plan to do in version 0.1.5 is:
+ not allow LowS signatures in the wallet at all.
+ at wallet load, if the wallet is inconsistent automatically perform a Wallet repair, which clears out all the tx and then resyncs.
This should eliminate this class of failure going forward.
I can't be totally sure, but I really don't think that the software is corrupting the files. It must be another explanation.
Great news, paputa!!!, I just recovered your wallet!!.
I already sent you a PM
Hope you're in contact with Jim to let him know what's causing this to begin with, he's going through another person's wallet to find out what happened/can be done: https://bitcointalksearch.org/topic/multibit-hd-013-password-no-longer-valid-1205068I already sent you a PM
I'm glad to hear something CAN be done.
Well, the problem with paputa's files was that they were corrupted. I can't know why the were like that, but it could be because of many reasons: improper shutdown, disconnecting the power source, hard drive malfunction, etc.
a freeze of the program caused this, i has close the wallet and reopen but the password hasn't work
Great news, paputa!!!, I just recovered your wallet!!.
I already sent you a PM
Hope you're in contact with Jim to let him know what's causing this to begin with, he's going through another person's wallet to find out what happened/can be done: https://bitcointalksearch.org/topic/multibit-hd-013-password-no-longer-valid-1205068I already sent you a PM
I'm glad to hear something CAN be done.
Well, the problem with paputa's files was that they were corrupted. I can't know why the were like that, but it could be because of many reasons: improper shutdown, disconnecting the power source, hard drive malfunction, etc.
Great news, paputa!!!, I just recovered your wallet!!.
I already sent you a PM
Hope you're in contact with Jim to let him know what's causing this to begin with, he's going through another person's wallet to find out what happened/can be done: https://bitcointalksearch.org/topic/multibit-hd-013-password-no-longer-valid-1205068I already sent you a PM
I'm glad to hear something CAN be done.
Great news, paputa!!!, I just recovered your wallet!!.
I already sent you a PM
I already sent you a PM
Thank you
good person but above all honest.
If you need to retrieve the wallet go to him, very good.
Thanks again!
I'm glad you trusted me without knowing me, I know that's the hard part
So, thank you, actually.
Great news, paputa!!!, I just recovered your wallet!!.
I already sent you a PM
I already sent you a PM
Thank you
good person but above all honest.
If you need to retrieve the wallet go to him, very good.
Thanks again!
Great news, paputa!!!, I just recovered your wallet!!.
I already sent you a PM
I already sent you a PM
@paputa Sorry that, in the end, you were not able to recover your bitcoins. We use the wallet words extensively in the recovery so without those options are limited.
Electrum is a very good wallet so I am sure you will have a good experience with that.
For your own peace of mind I recommend going through their recovery process (from the Electrum seed phrase) at least once. That way you will know what it entails and can see it working.
Regards,
Jim
Electrum is a very good wallet so I am sure you will have a good experience with that.
For your own peace of mind I recommend going through their recovery process (from the Electrum seed phrase) at least once. That way you will know what it entails and can see it working.
Regards,
Jim
thank you
@paputa Sorry that, in the end, you were not able to recover your bitcoins. We use the wallet words extensively in the recovery so without those options are limited.
Electrum is a very good wallet so I am sure you will have a good experience with that.
For your own peace of mind I recommend going through their recovery process (from the Electrum seed phrase) at least once. That way you will know what it entails and can see it working.
Regards,
Jim
Electrum is a very good wallet so I am sure you will have a good experience with that.
For your own peace of mind I recommend going through their recovery process (from the Electrum seed phrase) at least once. That way you will know what it entails and can see it working.
Regards,
Jim
With a member of bitcointalk,we have seen that the password is correct but the wallet damaged,however i have decided of using electrum
i got the service http://www.walletrecoveryservices.com without success
With MultiBit HD you can have 12, 18 or 24 wallet words but not 16.
There is also a datestamp (something like 1234/56) but that is always numeric.
The words for the wallet words will always be from the BIP39 word list, which is here:
https://github.com/bitcoinjs/bip39/blob/master/wordlists/en.json
if that is helpful.
There is also a datestamp (something like 1234/56) but that is always numeric.
The words for the wallet words will always be from the BIP39 word list, which is here:
https://github.com/bitcoinjs/bip39/blob/master/wordlists/en.json
if that is helpful.
i have found the words but are 16 words 
use Electrum to recover the coins then, (if the ''16 words'' means 16 word Recovery seed)
Jump to: