<p>You are probably deriving a legacy P2PKH address (addresses that start with 1) versus the bech32 P2WPKH address (addresses that start with bc1) that Exodus uses.</p>
<p>A single WIF private key can generate multiple address types, other wallets and software are likely defaulting to a different type which is probably why you are having trouble. This is the same for seed phrases as well.</p>
<p>Also just FYI Bitcore-lib is an old outdated library and is not compatible with modern address types. The code example you provide would create a legacy P2PKH address (start with 1).</p>

CC BY-SA 4.0
2021-02-03T18:57:45.953Z
2021-02-03T18:57:45.953Z
m1xolyd1an
<p>I'm trying to understand why I'm having a hard time at importing exodus private keys in other wallets like jaxx o scatter.</p>
<p>I can't understand why I don't get the public address from the private key with this script:</p>
<pre><code>var bitcore = require(&quot;bitcore-lib&quot;)
var privateKey = bitcore.PrivateKey.fromString(&quot;**** exodus private key ****&quot;)
console.log(privateKey.toAddress().toString())
</code></pre>
<p>I'm not able either to get the address from the seed phrase by using <a href="https://iancoleman.io/bip39/" rel="nofollow noreferrer">https://iancoleman.io/bip39/</a> indicating bip32 derivation path to m/0/0.</p>
<p>Could anyone tell me what I'm doing wrong?</p>

<address-generation><bitcore><private-key-export><exodus>
Exodus exported private key
José María Franco Fraiz
# Exodus exported private key

(Asked by: username_0 on 2021-02-03)

I'm trying to understand why I'm having a hard time at importing exodus private keys in other wallets like jaxx o scatter.
I can't understand why I don't get the public address from the private key with this script:
var bitcore = require("bitcore-lib")
var privateKey = bitcore.PrivateKey.fromString("**** exodus private key ****")
console.log(privateKey.toAddress().toString())

I'm not able either to get the address from the seed phrase by using https://iancoleman.io/bip39/ indicating bip32 derivation path to m/0/0.
Could anyone tell me what I'm doing wrong?

**Tags:** address-generation, bitcore, private-key-export, exodus


---

## 1 answers

### Answer by username_1 on 2021-02-03. Score: 2 | Accepted answer

You are probably deriving a legacy P2PKH address (addresses that start with 1) versus the bech32 P2WPKH address (addresses that start with bc1) that Exodus uses.

A single WIF private key can generate multiple address types, other wallets and software are likely defaulting to a different type which is probably why you are having trouble. This is the same for seed phrases as well.

Also just FYI Bitcore-lib is an old outdated library and is not compatible with modern address types. The code example you provide would create a legacy P2PKH address (start with 1).


---

