<blockquote>
<p>How is this possible?</p>
</blockquote>
<p>This might happen if you didn't tell Electrum to use the &quot;<a href="https://bitcoin.stackexchange.com/search?q=derivation+path">derivation path</a>&quot; that Bitcoin Core uses.</p>
<p>A less likely cause might be the &quot;<a href="https://bitcoin.stackexchange.com/search?q=gap+limit">gap limit</a>&quot;</p>
<hr />
<p>Related questions</p>
<ul>
<li><a href="https://bitcoin.stackexchange.com/q/78993/13866">Default derivation paths</a></li>
</ul>

CC BY-SA 4.0
2023-01-03T19:29:43.290Z
Thanks! It turned out to be the gap limit. Aligning this in Bitcoin Core and Electrum fixed the issue.
Pimlam
CC BY-SA 4.0
2023-01-03T11:46:46.440Z
2023-01-03T11:52:57.493Z
2023-01-03T11:52:57.493Z
RedGrittyBrick
<p>I got a full node (pruned) up and running with Bitcoin Core via Tor. I installed Electrum Personal Server (EPS) and connected my hardware wallet with Electrum via Tor. I generated a watch-only wallet in Bitcoin Core of my hardware wallet by providing the master public key in the config.ini file (no other master public keys, only the one of my hardware wallet as shown on Electrum). Everything works: I get the green circle in Electrum, saying I'm connected to (only) my own node, and I can watch my wallet in Bitcoin Core.</p>
<p>However, Bitcoin Core's &quot;receiving addresses&quot; show addresses that do not belong to my wallet according to Electrum. I tried to send a test amount to one of the addresses in Bitcoin Core that were not shown in Electrum. This transaction now shows in Bitcoin Core as belonging to one of my watch-only addresses but does not show in Electrum. The ismine(&quot;address&quot;) command in Electrum returns false. I also can't sign messages with the address in Electrum with my hardware wallet connected as Electrum says the address doesn't belong to the wallet.</p>
<p>I double checked that only one MPK is mentioned in EPS's config.ini file, and I also created a new wallet in Bitcoin Core and resynced the EPS. Same problem: my wallet now shows a different amount in Bitcoin Core (including the abovementioned address) than in Electrum (excluding that address). Bitcoin Core is showing many other addresses that are not present in Electrum, besides this one that I sent a test transaction to.</p>
<p>How is this possible? The Bitcoin Core wallet has private keys disabled + blank wallet and is named &quot;electrumpersonalserver&quot;, so it should be dedicated to EPS and since I only imported and master public key, shouldn't it contain only addresses derived from that one master public key?</p>
<p>Is the issue that Bitcoin Core has derived an address from my master public key that Electrum hasn't generated yet? But I'd think that Electrum should recognise all addresses that belong to the wallet (and ismine returned false and I can't sign messages with the address in my Electrum wallet as it says the address doesn't belong to the wallet). Or shouldn't I have imported the master public key through the EPS config.ini file (and rather imported it through the Bitcoin Core console)?</p>
<p>I would be very grateful for any help and insights into what's going on here. Many thanks in advance!</p>

CC BY-SA 4.0
2023-01-03T16:45:20.187Z
Uh, you specified something in Bitcoin Core's “config.ini”?  Did you mean `bitcoin.conf` or `wallet.dat`? Could you clarify which app you specified the MPK for and how you generated the “watch-only” address in Bitcoin Core?
Murch
CC BY-SA 4.0
2023-01-03T19:31:37.813Z
I was referring to Electrum Personal Server (EPS)'s config.ini file (not Bitcoin Core's files).
Pimlam
<bitcoin-core><electrum><public-key><full-node><address-generation>
Bitcoin Core shows addresses that Electrum says don't belong to my wallet (imported MPK via EPS). What is going on?
Pimlam
# Bitcoin Core shows addresses that Electrum says don't belong to my wallet (imported MPK via EPS). What is going on?

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

I got a full node (pruned) up and running with Bitcoin Core via Tor. I installed Electrum Personal Server (EPS) and connected my hardware wallet with Electrum via Tor. I generated a watch-only wallet in Bitcoin Core of my hardware wallet by providing the master public key in the config.ini file (no other master public keys, only the one of my hardware wallet as shown on Electrum). Everything works: I get the green circle in Electrum, saying I'm connected to (only) my own node, and I can watch my wallet in Bitcoin Core.

However, Bitcoin Core's "receiving addresses" show addresses that do not belong to my wallet according to Electrum. I tried to send a test amount to one of the addresses in Bitcoin Core that were not shown in Electrum. This transaction now shows in Bitcoin Core as belonging to one of my watch-only addresses but does not show in Electrum. The ismine("address") command in Electrum returns false. I also can't sign messages with the address in Electrum with my hardware wallet connected as Electrum says the address doesn't belong to the wallet.

I double checked that only one MPK is mentioned in EPS's config.ini file, and I also created a new wallet in Bitcoin Core and resynced the EPS. Same problem: my wallet now shows a different amount in Bitcoin Core (including the abovementioned address) than in Electrum (excluding that address). Bitcoin Core is showing many other addresses that are not present in Electrum, besides this one that I sent a test transaction to.

How is this possible? The Bitcoin Core wallet has private keys disabled + blank wallet and is named "electrumpersonalserver", so it should be dedicated to EPS and since I only imported and master public key, shouldn't it contain only addresses derived from that one master public key?

Is the issue that Bitcoin Core has derived an address from my master public key that Electrum hasn't generated yet? But I'd think that Electrum should recognise all addresses that belong to the wallet (and ismine returned false and I can't sign messages with the address in my Electrum wallet as it says the address doesn't belong to the wallet). Or shouldn't I have imported the master public key through the EPS config.ini file (and rather imported it through the Bitcoin Core console)?

I would be very grateful for any help and insights into what's going on here. Many thanks in advance!

**Tags:** bitcoin-core, electrum, public-key, full-node, address-generation

> **Comments:**
> **username_1**: Uh, you specified something in Bitcoin Core's “config.ini”?  Did you mean `bitcoin.conf` or `wallet.dat`? Could you clarify which app you specified the MPK for and how you generated the “watch-only” address in Bitcoin Core?  
> **username_0**: I was referring to Electrum Personal Server (EPS)'s config.ini file (not Bitcoin Core's files).  

---

## 1 answers

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

> How is this possible?

This might happen if you didn't tell Electrum to use the "[derivation path](https://bitcoin.stackexchange.com/search?q=derivation+path)" that Bitcoin Core uses.

A less likely cause might be the "[gap limit](https://bitcoin.stackexchange.com/search?q=gap+limit)"

---

Related questions

* [Default derivation paths](https://bitcoin.stackexchange.com/q/78993/13866)

> **Comments:**
> **username_0**: Thanks! It turned out to be the gap limit. Aligning this in Bitcoin Core and Electrum fixed the issue.  

---

