<p>You most likely mistyped one or several words.<br>
Manually trying different combinations can be a tedius process.<br>
If I were you, I would be using seed recovery tool like <a href="https://github.com/gurnec/btcrecover" rel="nofollow noreferrer">btcrecover</a>.</p>

<p>Are you familiar with the <a href="http://en.m.wikipedia.org/wiki/Levenshtein_distance" rel="nofollow noreferrer">Levenshtein distance</a>? The word(s) you misstyped are most probably the one(s) with shortest Levenshtein distance to the BIP32 spec words.  </p>

<p>Example: </p>

<blockquote>
  <p>st<strong>a</strong>ff can easily be mistaken for st<strong>u</strong>ff or vice versa, since both are BIP32
  words.</p>
</blockquote>

CC BY-SA 3.0
2018-01-04T00:20:07.560Z
Thanks. Wanted to use btcrecover but it doesn't seem to support Segwit BTC addresses (P2SH starting with 3).
migu
CC BY-SA 3.0
2017-12-31T13:18:24.710Z
2017-12-31T13:18:24.710Z
Chak
<p>I got locked out of my Ledger Nano S. When setting up the device I was given a 24 words seed passphrase, which I wrote down. The device asked me to verify 3 of the 24 words and my input was valid.</p>

<p>It now turned out that I made a mistake when writing the seed passphrase down since the checksum doesn't validate and I can't recover my wallets. All words that I wrote down are words that are in the <a href="https://github.com/iancoleman/bip39" rel="nofollow noreferrer">BIP32 spec words list</a>.</p>

<p>What strategy would you use (involving coding or not coding) to try and fix the seed passphrase?</p>

<bip32-hd-wallets><seed>
Seed recovery strategy
migu
# Seed recovery strategy

(Asked by: username_0 on 2017-12-31)

I got locked out of my Ledger Nano S. When setting up the device I was given a 24 words seed passphrase, which I wrote down. The device asked me to verify 3 of the 24 words and my input was valid.

It now turned out that I made a mistake when writing the seed passphrase down since the checksum doesn't validate and I can't recover my wallets. All words that I wrote down are words that are in the [BIP32 spec words list](https://github.com/iancoleman/bip39).

What strategy would you use (involving coding or not coding) to try and fix the seed passphrase?

**Tags:** bip32-hd-wallets, seed


---

## 1 answers

### Answer by username_1 on 2017-12-31. Score: 1

You most likely mistyped one or several words.  
Manually trying different combinations can be a tedius process.  
If I were you, I would be using seed recovery tool like [btcrecover](https://github.com/gurnec/btcrecover).

Are you familiar with the [Levenshtein distance](http://en.m.wikipedia.org/wiki/Levenshtein_distance)? The word(s) you misstyped are most probably the one(s) with shortest Levenshtein distance to the BIP32 spec words.

Example:

> st**a**ff can easily be mistaken for st**u**ff or vice versa, since both are BIP32
> words.

> **Comments:**
> **username_0**: Thanks. Wanted to use btcrecover but it doesn't seem to support Segwit BTC addresses (P2SH starting with 3).  

---

