<p>Exodus Desktop exports three extended public keys as far as I know. The first <code>xpub</code> belongs to your Legacy account at m/44'/0'/0', the second <code>zpub</code> to your Native Segwit account at m/84'/0'/0' and the third and final <code>zpub</code> to your Taproot account at m/86'/0'/0'.</p>
<p>Depending on which of these extended keys your customer used, your bitcoin may be at &quot;different locations&quot; in your wallet. For more information about this, see <a href="https://learnmeabitcoin.com/technical/derivation-paths" rel="nofollow noreferrer">this guide on derivation paths</a>. No reason to worry, if your customer did indeed correctly use one of your extended public keys, you will be able to recover everything.</p>
<ul>
<li><p>If the customer used the first <code>xpub</code>, his wallet probably derived Legacy addresses from it. You should be able to see balance on those addresses in Exodus after you enabled <em>advanced wallet mode</em> in the settings and toggled <em>Legacy Address</em> on the right when viewing your bitcoin balance.</p>
</li>
<li><p>They probably didn't use the second <code>zpub</code>, since that most likely wouldn't have caused any issues.</p>
</li>
<li><p>If they used the third <code>zpub</code> things may get a little more complicated. It's quite unlikely that the wallet software of your customer used this key to derive Taproot addresses and the bitcoin would now be sitting on Native Segwit addresses, but using the wrong path at m/86'/0'/0'.</p>
</li>
</ul>
<p>The latter and other similar scenarios <em>(such as Legacy addresses on m/84'/0'/0' or Native Segwit addresses on m/44'/0'/0')</em> can be recovered by manually deriving to the &quot;wrong&quot; path using the according script type. This can be easily done with <a href="https://sparrowwallet.com" rel="nofollow noreferrer">Sparrow Wallet</a> by disabling <em>validate derivations</em> in the settings, choosing the script type and changing the derivation path manually. Please only use these obscure accounts for recovery and not for actual usage in the future.</p>
<p>There is of course also the possibility that the customer scammed/tricked you into using an address that doesn't even belong to you. I just wanted to mention this but you probably know the circumstances better than I do.</p>
<p>I would generally recommend not to use extended public keys like this and instead <strong>always generate addresses yourself</strong>. That way you can verify the correct script type/path is used and verify the address belongs to you in the first place. There is also a privacy concern involved when you reveal your extended public key, since anyone knowing it can derive all addresses of the account in question, thus being able to see your total balance and transactions.</p>

CC BY-SA 4.0
2023-01-26T09:14:36.630Z
2023-01-26T09:14:36.630Z
sutterseba
<p>When you use xpub to generate address to receive funds, instead of using receive function wallet this happens. This is because the wallet hasn't looked ahead enough to <a href="https://insights.blockonomics.co/bitcoin-what-is-this-gap-limit-4f098e52d7e1/" rel="nofollow noreferrer">discover the funds</a>.</p>
<p>A simple fix for this is to force the wallet to discover / scan for funds. Here is a <a href="https://blockonomics.freshdesk.com/support/solutions/articles/33000241599-discovering-missing-funds-in-your-wallet#exodus" rel="nofollow noreferrer">detailed guide</a> to force rescanning for funds on exodus wallet.</p>

CC BY-SA 4.0
2023-01-26T10:31:33.110Z
2023-01-26T10:31:33.110Z
dark knight
<p>I am using the exodus wallet and I exported the xpub key because I used it for a shop to receive payments using btc. Someone bought my product and sent btc to a address generated with my xpub key but its not showing up in my exodus wallet.</p>
<p>How can I access that btc?(I have access to the private key and the seed phrase)</p>
<p>Thanks in advance!</p>

<xpub>
Access BTC balance using xpub key
bana28
# Access BTC balance using xpub key

(Asked by: username_0 on 2023-01-21)

I am using the exodus wallet and I exported the xpub key because I used it for a shop to receive payments using btc. Someone bought my product and sent btc to a address generated with my xpub key but its not showing up in my exodus wallet.

How can I access that btc?(I have access to the private key and the seed phrase)

Thanks in advance!

**Tags:** xpub


---

## 2 answers

### Answer by username_1 on 2023-01-26. Score: 1

Exodus Desktop exports three extended public keys as far as I know. The first `xpub` belongs to your Legacy account at m/44'/0'/0', the second `zpub` to your Native Segwit account at m/84'/0'/0' and the third and final `zpub` to your Taproot account at m/86'/0'/0'.

Depending on which of these extended keys your customer used, your bitcoin may be at "different locations" in your wallet. For more information about this, see [this guide on derivation paths](https://learnmeabitcoin.com/technical/derivation-paths). No reason to worry, if your customer did indeed correctly use one of your extended public keys, you will be able to recover everything.

* If the customer used the first `xpub`, his wallet probably derived Legacy addresses from it. You should be able to see balance on those addresses in Exodus after you enabled *advanced wallet mode* in the settings and toggled *Legacy Address* on the right when viewing your bitcoin balance.
* They probably didn't use the second `zpub`, since that most likely wouldn't have caused any issues.
* If they used the third `zpub` things may get a little more complicated. It's quite unlikely that the wallet software of your customer used this key to derive Taproot addresses and the bitcoin would now be sitting on Native Segwit addresses, but using the wrong path at m/86'/0'/0'.

The latter and other similar scenarios *(such as Legacy addresses on m/84'/0'/0' or Native Segwit addresses on m/44'/0'/0')* can be recovered by manually deriving to the "wrong" path using the according script type. This can be easily done with [Sparrow Wallet](https://sparrowwallet.com) by disabling *validate derivations* in the settings, choosing the script type and changing the derivation path manually. Please only use these obscure accounts for recovery and not for actual usage in the future.

There is of course also the possibility that the customer scammed/tricked you into using an address that doesn't even belong to you. I just wanted to mention this but you probably know the circumstances better than I do.

I would generally recommend not to use extended public keys like this and instead **always generate addresses yourself**. That way you can verify the correct script type/path is used and verify the address belongs to you in the first place. There is also a privacy concern involved when you reveal your extended public key, since anyone knowing it can derive all addresses of the account in question, thus being able to see your total balance and transactions.


---

### Answer by username_2 on 2023-01-26. Score: 0

When you use xpub to generate address to receive funds, instead of using receive function wallet this happens. This is because the wallet hasn't looked ahead enough to [discover the funds](https://insights.blockonomics.co/bitcoin-what-is-this-gap-limit-4f098e52d7e1/).

A simple fix for this is to force the wallet to discover / scan for funds. Here is a [detailed guide](https://blockonomics.freshdesk.com/support/solutions/articles/33000241599-discovering-missing-funds-in-your-wallet#exodus) to force rescanning for funds on exodus wallet.


---

