Problem when manually importing BIP32 derivation path

Describe the bug When user imports externally generated xpub it’s impossible to find a match.

To Reproduce the bug Steps to reproduce the reported bug:

1. Go to 'Electrum`, create legacy wallet, copy xpubkey.
2. Add xpubkey to btcpay
3. See address match - fail
4. Try to find a match by adding it into a hint field - fail

When you try with zpub the problem doesn’t happen.

Your BTCPay Environment (please complete the following information):

• BTCPay Server Version: 1.0.6.3 and 1.0.6.2
• Deployment Method: Docker
• Browser: Firefox

Logs (if applicable) Nothing much besides this which isn’t weird in nbx

info: Events:         BTC: New block 000000000000000000078b5f45cda077c8b1e3d32415af997b4026657a2473d2 (661406)
info: Events:         BTC: xpub6CQirZ...UJDvSHMCdgFaeeosZXU1 matching unconfirmed transaction cd7554...7fa72a (0/70)
info: Events:         BTC: New block 00000000000000000000554e4db347ead7e88066d80c2e4c919c805835934f2c (661407)
info: Events:         BTC: New block 00000000000000000008521e70152dafbfc5994d2096f628c1965c343534e14b (661408)
info: Events:         BTC: xpub6CQirZ...UJDvSHMCdgFaeeosZXU1 matching confirmed transaction cd7554...7fa72a (0/70)

Setup Parameters

Additional context

[Kukks]

@pavlenex
BIP32 is the HD address definition (how to create infinite addresses from one key) BIP39 is the seed phrase definition ( how to create one key from a set of words) BIP 44 defines legacy address derivation paths using BIP32 BIP 49 defines P2SH derivation paths using BIP32 BIP 84 defines segwit derivation paths using BIP32

I need to dig into Electrum a bit and see what they do. BIP32 does not tell you how to derive address for a wallet. Electrum seems to have its own that we need to see

[pavlenex]

Apparently I am drama queen at 1AM 😕

Explained the issue here it was wallet UI that was confusing.