[Solved] [Mycelium wallet] Missing addresses after importing seed into Electrum

[LoyceV]

I have a Mycelium wallet on Android, which works fine. But when I import the seed into Electrum, not all addresses show up. I see incoming transactions from 2020, but I don't see incoming transactions from 2025. I do however see the change that came from sending the transactions received in 2025!
Just in case, I tried increasing the gap limit to 500+, but that didn't help. All addresses are native Segwit addresses, so I'd expect all of them to use the same derivation path.
I now have Bitcoin in Mycelium that doesn't show up in Electrum using the same seed, and that doesn't feel right.

Any ideas where to start searching for a cause?

[Mia Chloe]

I have a Mycelium wallet on Android, which works fine. But when I import the seed into Electrum, not all addresses show up. I see incoming transactions from 2020, but I don't see incoming transactions from 2025. I do however see the change that came from sending the transactions received in 2025!

I thought this is a bug mycellium should have fixed a long time ago but trust me it is the reason why I stopped using mycellium. Two things could be the issue, one case is improper syncing where some coins go missing and second is derivation path problems.
First  ill suggest you import those keys to blue wallet and see if you get all your coins and addresses loaded up because sometimes in the past when I tried it worked on the go.

If blue wallet didn't work then I think the problem is Electrum isn’t deriving addresses from the same derivation path Mycelium used for those new addresses. I think mycelium added Taproot support around 2024 so your 2025 addresses might actually be Taproot (BIP86) while your older 2020 ones were SegWit (BIP84).

Sometimes Electrum won’t automatically scan multiple derivation paths unless you tell it to so I'm guessing it's picking only m/84'/0'/0' But you can manually select the correct derivation type. After putting the seed in Electrum, Click on Check BIP39 seed and try;

Code:

m/84'/0'/0' (for bc1q addresses)
m/86'/0'/0' (for bc1p Taproot addresses)

Electrum should generate new wallets for each of them then check which one contains your 2025 transactions.

[Charles-Tim]

Sometimes Electrum won’t automatically scan multiple derivation paths unless you tell it to so I'm guessing it's picking only m/84'/0'/0' But you can manually select the correct derivation type. After putting the seed in Electrum, Click on Check BIP39 seed and try;

Electrum will asked for the script type and the derivation path before you can proceed. LoyceV chose the right one which is also the default. That is the reason he saw some transactions history there.

Maybe some transactions there on Mycelium are P2TR but which Electrum does not yet support.

[LoyceV]

I think mycelium added Taproot support around 2024 so your 2025 addresses might actually be Taproot (BIP86) while your older 2020 ones were SegWit (BIP84).

Thanks, this must be the reason. I completely forgot to look at the 4th character of the addresses, and indeed, they are different. The fact that the change shows up in Electrum is probably a privacy feature in Mycelium: it makes sense to send change to the same address format, to make it harder to know which output goes to change.

[Mia Chloe]

Thanks, this must be the reason. I completely forgot to look at the 4th character of the addresses, and indeed, they are different. The fact that the change shows up in Electrum is probably a privacy feature in Mycelium: it makes sense to send change to the same address format, to make it harder to know which output goes to change.

When I encountered this particular problem the most was when I was using mycellium in my newbie days and you know how it feels when you discover some bitcoins are missing and you didn't spend any. Ever since then I just settled for Electrum standard seed since they save you the stress most of the time.

Electrum will asked for the script type and the derivation path before you can proceed. LoyceV chose the right one which is also the default. That is the reason he saw some transactions history there.

Most wallet prefer to settle for the first derivation path they find as they scan and sync so increasing the gap limit sometimes still will not help.

[LoyceV]

This issue is mainly caused by the difference in derivation path

Did you even read the 4 posts in this topic?

I'll lock this now.