Ledger Nano S does not recognise my BTC Segwit Receive Address it issued

[RDH40]

My Ledger Nano S issued me the following BTC Segwit receive address:36ezRREzDYH3uSvADoSSpoLZrFVigQkmLp
I transferred 3.31 BTC to this address on 27th December 2017 and have not been able to access or retrieve them since.
Ledger Support can't/won't help me and insist that this address did not come from my wallet or 24 word seed. It definitely did.
This transaction was done with the old chrome apps and my Ledger firmware is 1.3.1 - I have not updated the firmware in fear of completely losing my coins altogether.
I notice on the blockchain that there is an exact same address relating to BCH - not sure why this is?
I have also tried Electrum and different derivation paths etc and still no joy.
I also transferred LTC & XRP to my Ledger at the same time which worked ok so this is very frustrating and confusing.
Anyone got any idea how I can access/retrieve my coins?

[1715460072]

1715460072

[LoyceV]

Ledger Support can't/won't help me and insist that this address did not come from my wallet or 24 word seed.

How would they know? Does Ledger not allow the creation of Segwit compatible addresses (starting with a 3)?

I notice on the blockchain that there is an exact same address relating to BCH - not sure why this is?

That's normal: BCH uses the same addresses. The address isn't funded on the BCH-chain, so just ignore it.

Anyone got any idea how I can access/retrieve my coins?

Have you tried IanColeman? If you try this, do it offline from a Live Linux DVD (running from RAM). Don't risk compromising your 24 words by touching an online device.

This transaction was done with the old chrome apps

Did you verify address 36ezRREzDYH3uSvADoSSpoLZrFVigQkmLp on the Ledger's own screen before sending the transaction?

[Charles-Tim]

According to your explanations, you have tried to use seed phrase importation to recover your bitcoin balance? I hope also that you first tried to use electrum wallet latest version as the wallet extension? Because the firmware version might have been old and not new which means you can also update that before doing any other thing. If all these truly have failed, what you will need to check next is the know (verify) if the address is connected to a private key on your wallet using your seed phras generated.

As suggested by LoyceV, use iamcoleman offline, input your BIP39 seed phrase, then scroll down. You will see Derivation paths, click on BIP49 which is nested segwit, then scroll down. You will be able to see the nested segwit derivation paths, private keys and addresses. Look at the addresses, check if you see any address you posted above.

I notice on the blockchain that there is an exact same address relating to BCH - not sure why this is?

Bitcoin cash forked in August 1, 2017 while you transfered to the address on December 2017. Supposing you have transferred the bitcoin to the address before bitcoin cash forked, you will be able to track the forked coins on blockchain explorer that you have certain forked coins and their balances. That is the reason you saw the Bitcoin cash, Bitcoin sv and any other forked coin, but although amounts to zero.

[Rath_]

How would they know? Does Ledger not allow the creation of Segwit compatible addresses (starting with a 3)?

They do. You could create such addresses in the old Chrome app and you can still do it in the Ledger Live. If OP told Ledger that he had tried multiple derivation paths in Electrum then that might be why they insist on saying that the address does not belong to his wallet.

I have also tried Electrum and different derivation paths etc and still no joy.

What derivation paths did you try specifically?

[HCP]

My Ledger Nano S issued me the following BTC Segwit receive address:36ezRREzDYH3uSvADoSSpoLZrFVigQkmLp

Do you remember exactly how you got this address from the Chrome app?

Did you click the "receive" tab in the Chrome app and it was displayed onscreen... or did you select it from a drop down list box?

If you got it from the drop down list box, then there is a chance that it is actually a "change" address... or that it is out past the gap-limit on most wallets. The dropdown list was not meant to be a way to get "receive" addresses... and was not "ordered". It has caused several users problems locating their coins in the past.

If it's a "change" address, you'd need to modify the derivation paths you're looking in ever so slightly... ie. m/49'/0'/0'/0/0 would become m/49'/0'/0'/1/0
If there is a possibility that it was out past the "gap-limit", you'd need to try using a wallet that supports modifying this (Ledger Live does, but you'd need to update your firmware).


The other possibility, although highly unlikely given the address is still funded after 3+ years, is that you had a clipboard malware back in December 2017, and when you sent the coins, the address you likely "pasted" (into whatever wallet/service that you transferred the 3.31 BTC from) was replaced with a hackers address. However, it is highly unlikely this is the cause because the coins haven't moved.

[RDH40]

My Ledger Nano S issued me the following BTC Segwit receive address:36ezRREzDYH3uSvADoSSpoLZrFVigQkmLp

Do you remember exactly how you got this address from the Chrome app?

Did you click the "receive" tab in the Chrome app and it was displayed onscreen... or did you select it from a drop down list box?
Yes, it displayed it on the screen with a QR code you can also scan. I took a screen shot of it so it is definitely correct.

If you got it from the drop down list box, then there is a chance that it is actually a "change" address... or that it is out past the gap-limit on most wallets. The dropdown list was not meant to be a way to get "receive" addresses... and was not "ordered". It has caused several users problems locating their coins in the past.
No, I did not select it from a drop down list.

If it's a "change" address, you'd need to modify the derivation paths you're looking in ever so slightly... ie. m/49'/0'/0'/0/0 would become m/49'/0'/0'/1/0
If there is a possibility that it was out past the "gap-limit", you'd need to try using a wallet that supports modifying this (Ledger Live does, but you'd need to update your firmware).


The other possibility, although highly unlikely given the address is still funded after 3+ years, is that you had a clipboard malware back in December 2017, and when you sent the coins, the address you likely "pasted" (into whatever wallet/service that you transferred the 3.31 BTC from) was replaced with a hackers address. However, it is highly unlikely this is the cause because the coins haven't moved.

Unlikely but even Ledger Support reckon this address did not come from my xpub? I even converted it to the pub and nothing shows?!

[RDH40]

Ledger Support can't/won't help me and insist that this address did not come from my wallet or 24 word seed.

How would they know? Does Ledger not allow the creation of Segwit compatible addresses (starting with a 3)?
Yes they do, and the BTC Segwit address my Ledger issued me starts with 36ez............

I notice on the blockchain that there is an exact same address relating to BCH - not sure why this is?

That's normal: BCH uses the same addresses. The address isn't funded on the BCH-chain, so just ignore it.
Ok

Anyone got any idea how I can access/retrieve my coins?

Have you tried IanColeman? If you try this, do it offline from a Live Linux DVD (running from RAM). Don't risk compromising your 24 words by touching an online device.
What would this achieve if Ledger Support insist that my address did not come from either my 24 words or xpub?

This transaction was done with the old chrome apps

Did you verify address 36ezRREzDYH3uSvADoSSpoLZrFVigQkmLp on the Ledger's own screen before sending the transaction?
You didn't get given the option to verify the address back then with the chrome apps.

[HCP]

Do you remember exactly how you got this address from the Chrome app?

Yes, it displayed it on the screen with a QR code you can also scan. I took a screen shot of it so it is definitely correct.

So, you still have this screenshot? If you scan it now, does it show the same address?

Have you tried IanColeman? If you try this, do it offline from a Live Linux DVD (running from RAM). Don't risk compromising your 24 words by touching an online device.

What would this achieve if Ledger Support insist that my address did not come from either my 24 words or xpub?

Ledger are likely just looking at your seed/xpub and then just using their standard derivation path's to check what addresses are being generated... it's possible that, for whatever reason, this came from a slightly different derivation path... in which case, using the Ian Coleman tool would let you experiment with different derivation path's easily.



Also, please learn to use the "quote" tags properly... you're putting your replies in the middle of quotes and it makes it VERY difficult to tell what is your response and what was the original question. If you want to reply "inline"... then you need to use the [ /quote ] tag... then type your reply... then put in a new [ quote] tag so it starts the quote correctly again... Otherwise, just put your answers all at the bottom.