<p>The mnemonic standard is BIP 39, and that is not the problem. The problem is the derivation paths.</p>

<p>Exodus, Jaxx, Coinomi, and many other wallets use the BIP 44 specification for deriving keys. This means the <code>m</code> for those wallets is actually the key at the path <code>m/44'/0'/0'</code>. However in your code with NBitcoin, you are using direct BIP 32 paths, so your <code>m</code> is actually <code>m</code>. So in NBitcoin, your keypath is actually <code>m/0/0</code> but in other wallet software, the path is <code>m/44'/0'/0'/0/0</code></p>

CC BY-SA 3.0
2017-10-03T18:32:57.357Z
2017-10-03T18:32:57.357Z
Ava Chow
<p>I am very new to Bitcoin development so forgive me...</p>
<p>I'm using NBitcoin in a .Net console app to generate a master key using a mnemonic and then derive hierarchical keys. Here is the code I am using:</p>
<pre><code>Mnemonic mnemo = new Mnemonic(Wordlist.English, WordCount.Twelve);
ExtKey hdroot = mnemo.DeriveExtKey();
var wif = hdroot.GetWif(Network.Main);
var defaultAddress = hdroot.Derive(new KeyPath(&quot;m/0/0&quot;));
</code></pre>
<p>Here is the Mnemonic I get as a result, as wells as a public address derived from the master key using the <strong>&quot;m/0/0&quot;</strong> path:</p>
<blockquote>
<p><strong>Mnemonic:</strong> dry brown drive parade drastic shine embrace hard report loan fold iron</p>
<p><strong>Path: m/0/0/:</strong> 1GcchMaHAN1XRQsoi8gPg8TShqzN4sNGvu</p>
</blockquote>
<p>I tested recreating my keys using the mnemonic and was always able to derive the same exact keys as expected within my console app.</p>
<p>Being curious I wanted to see if I could import this mnemonic into existing wallet software and get the same keys as well. Since the Exodus wallet uses a standard twelve word mnemonic I fired it up and generated my wallet using the same mnemonic. However none of the keys match up! I exported my public key and made sure it was the same path of &quot;m/0/0&quot; from the master. As you can see it is NOT a match:</p>
<p><strong>Exported public key from Exodus using the same mnemonic:</strong></p>
<blockquote>
<p><strong>Mnemonic:</strong> dry brown drive parade drastic shine embrace hard report loan fold iron</p>
<p><strong>Address:</strong> 1DMDJ266gxMCJiTcWk5MZFbfxxx4Ss3URN</p>
<p><strong>Path:</strong> m/0/0</p>
</blockquote>
<p>I also tested the mnemonic on Jaxx as well as the the Coinomi wallet on Android and it derived the same keys as Exodus does.</p>
<p>So I am completly confused. The only thing I can think of is that there is a standard entropy that these wallets use that is missing from my implementation?</p>
<p>My question is, how can I use NBitcoin to create the same mnemonic standrad that wallets like Exodus, Coinomi and Jaxx use?</p>

<bip32-hd-wallets><deterministic-wallets><nbitcoin><mnemonic-seed>
NBitcoin and Mnemonic Standards
INNVTV
# NBitcoin and Mnemonic Standards

(Asked by: username_0 on 2017-10-03)

I am very new to Bitcoin development so forgive me...

I'm using NBitcoin in a .Net console app to generate a master key using a mnemonic and then derive hierarchical keys. Here is the code I am using:

```
Mnemonic mnemo = new Mnemonic(Wordlist.English, WordCount.Twelve);
ExtKey hdroot = mnemo.DeriveExtKey();
var wif = hdroot.GetWif(Network.Main);
var defaultAddress = hdroot.Derive(new KeyPath("m/0/0"));

```

Here is the Mnemonic I get as a result, as wells as a public address derived from the master key using the **"m/0/0"** path:

> **Mnemonic:** dry brown drive parade drastic shine embrace hard report loan fold iron
>
> **Path: m/0/0/:** 1GcchMaHAN1XRQsoi8gPg8TShqzN4sNGvu

I tested recreating my keys using the mnemonic and was always able to derive the same exact keys as expected within my console app.

Being curious I wanted to see if I could import this mnemonic into existing wallet software and get the same keys as well. Since the Exodus wallet uses a standard twelve word mnemonic I fired it up and generated my wallet using the same mnemonic. However none of the keys match up! I exported my public key and made sure it was the same path of "m/0/0" from the master. As you can see it is NOT a match:

**Exported public key from Exodus using the same mnemonic:**

> **Mnemonic:** dry brown drive parade drastic shine embrace hard report loan fold iron
>
> **Address:** 1DMDJ266gxMCJiTcWk5MZFbfxxx4Ss3URN
>
> **Path:** m/0/0

I also tested the mnemonic on Jaxx as well as the the Coinomi wallet on Android and it derived the same keys as Exodus does.

So I am completly confused. The only thing I can think of is that there is a standard entropy that these wallets use that is missing from my implementation?

My question is, how can I use NBitcoin to create the same mnemonic standrad that wallets like Exodus, Coinomi and Jaxx use?

**Tags:** bip32-hd-wallets, deterministic-wallets, nbitcoin, mnemonic-seed


---

## 1 answers

### Answer by username_1 on 2017-10-03. Score: 1 | Accepted answer

The mnemonic standard is BIP 39, and that is not the problem. The problem is the derivation paths.

Exodus, Jaxx, Coinomi, and many other wallets use the BIP 44 specification for deriving keys. This means the `m` for those wallets is actually the key at the path `m/44'/0'/0'`. However in your code with NBitcoin, you are using direct BIP 32 paths, so your `m` is actually `m`. So in NBitcoin, your keypath is actually `m/0/0` but in other wallet software, the path is `m/44'/0'/0'/0/0`


---

