Open iancoleman opened 7 years ago
Dear Ian/Mr. Coleman,
I 'm desperately trying to write to anyone who I think might be able to help. Since my last ledger nano s update about 6 weeks ago I'm not able to get access to my assets. I tried my passphrase (which I used for last time on 2018), and I had no luck. Ledger recommended your standalone bip39 site. I have all 24 words but it appears that only 17 of them are in the correct order. When I use other orders (for the whole 24 words) the checksum is correct but I get completely different public addresses from what I have used for the last 2,5 years.
Ledger Co. Tells me that I wrote my passphrase wrong. There are many people out there with the same problem. Are we all that dumb to make such a mistake?
I have tried BTCrecover and Seedrecover but it didn't help. It only shows the option „Up to three mistakes 1 of which could be a completely different seed word“.
I'm not a programmer but if there's one thing I know it is threre's always a way. If the government organisation could do that, there also must be a way for individuals.
It's about 2,3 BTC worth of BTC and altcoins. My 2 years and all my savings.
Please let me know if you know of a way, a program, someone who could help. I have all the Xpubs and all my transactions are legit (from exchanges that I'm 100% verified). I wouldn't mind letting my computer run (even for years if necessary) to look for the right passphrase.
Thank you
Hello and thank you so much for replying,
it is BTC, DGB, XRP, and there are also external wallets for TRX, NEO, VeChain. which all needs the same private key from Ledger to unlock. And also ERC20 token on Myetherwallet. The one and only BTC address I have and used the whole time is a segwit address.
I tried to enter the derivation path shown on my ledger's advanced logs which is 49'/0'/0'/0/1 but I get the message on bip39-standalone.html "first character must be m".
The Passphrase is the reason for all these complications, I'll try to explain as best as I can, The ledger nano s Passphrase is a 24 words passphrase. After my ledger got stuck during the update to firmware 1.5.5 I had to re-enter the passphrase which I couldn't (it was shown as invalid). So I tried the first 12 words (successful) then the 18 words (unsuccessful) I tried every possibility for every word I thought I might have written down wrong. By the 16th words after changing it to all the possible words in trezor dictionary I got the 18 correct words (at least I thought so). Then I tried the passphrase with 24 words (unsuccessfully) I entered the last 6 words in an internet site which gives you every possible combination for these 6 words I guess there were 720 and I tried them one by one. After trying 90 or 92 possibilities I got the right order (which again was not the right order because I still don't get the same public addresses from my ledger.
I then tried my original passphrase in the left/right order, I mean instead of the,
1 13 2 14 3 15 4 16 5 17 6 18 . . 12 24
Which I have written on my original sheet , I tried them like, 1 / 13 / 2 / 14/ 3/ 15 and so on. The strange thing is when I do this, the Checksum is completely correct. and even the original 16th word, written down 2,5 years ago which on my first try didn't work is correct. And with this order the Passphrase is only shown as correct when I use the whole 24 words combination. The other combinations 12 words and 18 words are shown as invalid Mnemonics!
I really don't know what to do. Please let me know if there was something unclear or any information you might need.
As I have mentioned there are many people with the same problem. I think some of them have moved on unfortunately I can not afford to.
And thanks again for telling me that you're going to research.
On Sat, Mar 30, 2019 at 11:34 AM iancoleman notifications@github.com wrote:
Is it bitcoin or is it a different coin?
Things to check:
- the derivation path is correct
- the passphrase is correct
- various combinations of the words in the mnemonic
This is an interesting problem and I think a piece of software to help recover mistakes would be helpful. I'll think about what that might look like and maybe write some code since it's a useful thing to have. Looks like BtcRecover is pretty good, but I've only glanced at it. Let me think and research on this topic for a while.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/iancoleman/bip39/issues/82#issuecomment-478232643, or mute the thread https://github.com/notifications/unsubscribe-auth/AhrZVfNyhbHnxw9j39YTaevDzfdHQuLUks5vbz24gaJpZM4OLveR .
Dear Ian,
Thank you so much for replying and for the moral support. I've got my funds back thanks to this wonderful guy https://grnqrtr.com/ which I have found reading the blog of this other wonderful guy http://damien.la/2017/09/10/mnemonic
Thanks to all of you guys for being there.
This is a list of prerequisites before releasing v1.0.0
BIP39 status change from Proposed to Final https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki
BIP44 status change from Proposed to Final https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki