Topic: Ledger doesn't show transaction, it shows up in Electrum. What's going on? - page 2. (Read 363 times)

What address type did you get from BlueWallet as receive address where you sent coins to (1..., 3... or bc1...)?



Now it gets a bit confusing. You say Electrum and BlueWallet have same receive adress, but it's not a native segwit type starting with bc1. This is how I understand what you wrote, correct me if I'm wrong. Addresses in Ledger Live are bc1?

I don't use Ledger crap and Ledger Live isn't the finest piece of software engineering. Can you switch address type in Ledger Live to match receive address type used with BlueWallet? Does then the transaction show up?



OK, so all xpubs match and likely are the same as your Ledger hardware would communicate to a software wallet if you'd connect it to a wallet. I assume you screwed up with the address type and/or derivation path.

Thanks for all your input, very much appreciated.

I think the only thing that was a little unusual is that I used Blue Wallet (with the xpub) to get the "receive" address. I didn't generate it or validate it on Ledger. I didn't think that was a problem, guess I was wrong. In Blue Wallet, in the watch only wallet, there's a Receive button that I clicked, no options or anything, it comes up with receive address in the format of a QR code and also a string.

I just checked all locations (Ledger Light, Electrum, Sparrow, and Blue Wallet). The xpubs all match.

To get the xpub from Ledger Light, I followed this process: https://support.ledger.com/hc/en-us/articles/360011069619-Extended-public-key-xPub?docs=true

Electrum and Blue Wallet have the same next Receive address
Sparrow looks different, they start with bc1. It may be because of the current derivation path (m/84'/0'/0') which I've messed with a bit, don't really understand the derivation path but I do understand it's important.

The next address on the Ledger ALSO starts with bc1, and is identical to the one in Sparrow. Neither Sparrow or Ledger find the transaction. Hmm...

I went into Electrum and tried creating a new device, connecting to hardware device, etc. But it says "no hardware device detected" even when the ledger is plugged in.

I will try the xPub scanner tool if I have to, it looks like it's above my head, though.

The title is highly deceptive. Open your Ledger, select Bitcoin app and make in Electrum a new wallet off that
Until then I agree with @nc50lc: the xpub is most probably unrelated to your Ledger addresses.


I would start with same setup, i.e. actual Ledger in Electrum. Then find out how that odd xpub has transactions. Isn't that the right way?

I don't think it's clipboard malware because OP said that the balance is also shown in the Electrum wallet.

What I think is nc50lc might be right that the other wallet like Bluewallet and Ledger Live have different derivation paths.

@OP would you mind to try to use the xPub scanner developed by Ledger it can be used to find the addresses with balances and the right derivation path. You can find the tool from the link below.

- https://github.com/LedgerHQ/xpub-scan

Let's hope that it can find the address generated from Bluewallet where you received BTC with the right derivation path so that you can later use that path to Ledger Live and Sparrow.

Here is the Ledger guide on extracting an xpub - https://support.ledger.com/hc/en-us/articles/360011069619-Extended-public-key-xPub
Did you follow these steps?

If you go back in to Ledger Live and extract the xpub again, does it match the xpub you are importing to all these different wallets?

You say the transaction does not show up in Ledger Live or in Sparrow. Do these wallets show different addresses to Blue and Electrum, or are the addresses the same but just with no transaction?

Did you at any time confirm that the receiving address on Blue Wallet is the same as the one displayed on the screen of your Ledger hardware wallet? Did Blue Wallet and Ledger request such address verification when you generated the receiving address?

I doubt it's a clipboard malware. OP can see the transaction they made in their Blue Wallet. If it was a clipboard malware, the destination address would be something completely unrelated to any of their addresses.

My immediate guess is the copied xpub isn't related to any of your account in Ledger Live.
It can also be something like extended derivation done by Blue wallet to the provided xpub or as simple as different address type.
The worst case scenario is if it's changed from your clipboard by a malware.

As for Electrum, it derives the 'internal chain' and 'external chain' paths after the provided xpub,
for example: your_xpub/0/receiving_address_0+ & your_xpub/1/change_address_0+
In Electrum, the script type for "xpub" is standard P2PKH; in Sparrow, it depends on what you've selected.

Describe how you set-up your Ledger Device, the exact steps including the software used and which part of the client you've exported the xpub.

You can also tell how you imported the xpub to Blue wallet because AFAIK, Blue Wallet follows whatever path where it found any related transactions.
If it didn't find any, it wont let you import the extended master public key.

Hope this provided enough hint before clarifications are provided.

I set up a Ledger device a while back. Then I put the Xpub from the Ledger device on BlueWallet (set up as a Watch Only Wallet). I then used the receive address that I got from BlueWallet to receive some bitcoin.
The transaction showed up in BlueWallet. However, it never showed up in Ledger Live. I imported the Xpub into Electrum, and the transaction DOES show up there.
However, it does NOT show up in Sparrow when I import the xpub.
I'm thinking that somehow the receive address that BlueWallet generated is not one that either Ledger or Sparrow would check. I've tried turning on the "extended account search" in Ledger Live, and also increasing the "custom gap limit" in Ledger Live to what I believe is the max (from 20 to 999), and the transaction still doesn't show up (even after I clear the cache).

Any thoughts?