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............

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

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?

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.

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?!

What is most probable is that the OP noted down the seed incorrectly.

Recovered it and then couldn't access his funda again


Another option is that the OP sent his funds to the incorrect address.  Or a copy paste virus or something like that.

The most unlikely situation is that the OP's leddger nano has a terrible bug, which gave him the wrong address.

This is very unlikely because there are no reports like that.

I sincerely doubt that your Ledger would generate an address not related to your xpub.

Where did you get/made the segwit receive address?
Did you get it from Ledger live or in Electrum?

I got this BTC Segwit receive address from my Ledger Nano S via the original way through the Bitcoin Ledger Wallet Chrome App

Have you tried to export your account from Ledger Nano?
If not try to export them first and maybe you can find your wallet there.

Guides can be found here Export your accounts from ledger

If not can you explain a bit more if what procedure did you do to get the Segwit address?

@RHD40, i am still waiting for our reply , did you do exactly what i said? you should have recovered the coins by now, if not you can shoot me a PM.

Unless you tick the "remember my choice" option, the "Ledger Wallet Bitcoin" Chrome App asks on startup:



However, as it displayed a "3" type address (as proven by the posted photo)... the Ledger wallet should only have done this if the OP had selected "SegWit"... it's the only scenario in which you should get P2SH addresses from a Ledger wallet (even if you were using LTC prior to the change to "M" type addresses for LTC).

As things stand, I can only think of a few causes for this issue:

1. Previously unknown (but theoretically possible) malware that changed the "receive" address displayed by the older versions of the wallet. However, given that the 3.3 BTC has NOT been moved from that address, I'd guess that this is somewhat unlikely. Yes, I agree

2. It was actually an old LTC SegWit address using the "3" type addresses before Ledger upgraded. The screenshot says "BTC" but it might have been a graphical glitch in the older wallet... I can't confirm one way or the other as I can't get an old version of the wallet to test. If this is the case, it might be possible to use the solution provided by cryptonerddy. I tried this but nothing

3. Glitch with the derivation path used by the wallet. I've not seen another case of this before, but a lack of evidence does not disprove this theory.

4. The wallet that the address was generated from was NOT "Account 0"... but Account 1 or 2 etc. I'm unsure how likely this is... I believe the Ledger wallet shows an overview of ALL (used) accounts as the default dashboard... but still a possibility.

5. The wallet that the address was generated from was protected by BIP39 passphrase... OP claims they never used passphrase with this wallet (somewhat supported by the fact that they can see the BCH and LTC balances without needing to use a passprhase)

6. Something else... ? ? ?

It seems I'm doomed! Think we've run out of all possibilities!

@HCP you've tried to help him last time back in january
both of you might want to review what has been done and continue from that point

just pointing out some important points for clarification
- you resetted your ledger, written down the new 24 word seed
- obtained one BTC address & one LTC address and give them to your friend to receive some BTC & LTC
- both confirmed on its respective chain, but you no longer see BTC address in your ledger

just my thought on what you should check
- try iancoleman BIP39 with your old seed, I assume you've tried with new seed and not found
I don't have the old seed but I never obtained any addresses from this anyway - I never got that far
- is this 36ezRREz... address exist in your LTC receive address? (probably not but...)
No it doesn't
- then I'm pretty sure you have the wrong seed used (address was from old seed) or LTC/BTC mismatched use
The 24 word seed is definitely correct
- is it possible somehow your Mxxx LTC address was used and translated to its corresponding 3xxx address that you received on BTC chain
No this has not happened

I know all these suggestions sound far fetched,
but for 3.30941541 BTC you should try everything, even the unthinkable or impossible

Do this
Download Electrum LTC on your PC
Open it, click new wallet> standard wallet> i have seed> put the right seed there> click next then your wallet will be created. go to the address tab and look for this address MCs8jJexAf8UhxC4KgRneSayAx6Aincbbz
right click and copy the private key.
go to liteaddress.org click on the wallet details tab> paste the private key there. now copy the hexadecimal key given at the bottom of the page.

go to bitaddress.org, also go to the wallet details tab and paste the hexadecimal key there, it should give you two addresses and two different keys. copy the compressed private key and go to segwitaddress.org, scroll down to the last tab and paste the key there, you'll find that it matches the address.

now import the key into electrum and your coins would show

here's my address, leave a big tip 19Q2fJ2qEfLXnYpQU7eqAGCeucK8NVapw6

As i said earlier i had the exact same issue with my trezor and the people  here gave me suggestions and it turns out i made an error with my seed phrase, don't give up and try to exhaust all possibilities. Do as they have suggested by posting an image here and i really don't see what the big deal is by posting the image, except you're wrong?

Ahhhhh this brings back memories... not sure why that thread feel off my notifications list? I never noticed that the OP had made the final reply??!? Apologies for that.

Right, I have to ask the obvious question then... Given that you were copying both LTC and BTC addresses... I assume you checked the LTC "sign message" list for what you believe is the BTC address?

Or used the iancoleman.io tool and set the coin to LTC with your seed and checked those addresses for what you think is the BTC address?

Actually that is exactly what posting the photo will prove... Because then we'll be able to know if the photo matches the address you have stated.

It will also show that the address you sent to was displayed within your Ledger wallet.

What you need to understand is that there have been numerous instances of users on this forum claiming that "it was typed 100% correct"... Only to discover later that in fact the password or recovery seed or address was in fact typed incorrectly.

At this moment, we only have your word for it. It's nothing personal, and given how adamant you are, I'm sure it's true... But a copy of the photo would prove it 100%

You cannot post images because you are a newbie in this forum.
If you post the photo on some website like imgur.com, just link the address here and I will post for you.

An address can easily be mistyped....
o instead of 0 for example, S and 5, I and l

I never tried to type an address, always ctrl C + ctrl V.

This issue has nothing to do with signing messages... what Lucius was talking about was copying an address from the "Sign message" dropdown list of addresses rather than clicking on the "Receive" tab...

When you use the "Sign Message" dropdown box... it shows several hundred addresses and I believe it actually includes "change" addresses as well. In addition, these addresses are not necessarily displayed in chaincode order... so the first address displayed is not necessarily address m/49'/0'/0'/0.

The issues this causes are that if you use one of the addresses from this dropdown list as a "receive" address... it's possible you're actually selecting some address way down the chain like address m/49'/0'/0'/87... which is likely to be out past the "gap limit" that the Ledger wallet is using when looking for addresses with transaction history etc. So, if you receive coins to it, Ledger wallet won't find the transaction.

Anyway, this situation doesn't seem to apply to the OP as they're saying they used the "receive" tab, which should use the first "unused" receive address. So, they either entered the Bitcoin address incorrectly (although I'm not even sure what the odds of generating a valid address when mistyping an address are? )... or they're done something weird like accidentally use a Litecoin address or something like that.

It would help if the OP still has the photo they took of the original address... without that it will be difficult to prove/disprove the mistyped address scenario. Although, using the "Signed Message" option, you can start typing an address and it shows the partial matches. ("Settings -> Tools -> Sign Message", click the "Address" box and type the first couple of characters of the address).

Sorry I mistyped, QR code.
It's a picture that can be scanned to transfer funds without typing or copying pasting the address.

Ok, as you bought directed from ledger you were not scammed.

Did you use a passphrase? It's like a 25th word. You can unlock a second hidden ledger nano wallet using a different pin. Did you use that?
https://support.ledgerwallet.com/hc/en-us/articles/360000783134-How-to-set-up-and-or-recover-a-hidden-passphrase-and-alternate-PIN-on-your-Ledger-Nano-S-H

There is no problem regarding security when you copy and paste an address, because it's a public address and nobody can take your funds using it.

Exactly.

But when you take a photo, there is the risk you mistyped it... You could have used the we code at least.

I definitely did not mistype it. When you say we code - what do you mean?

Anyway,  have you tried to use iancoleman.io and recover that address privatekey? Yes
If it's not there, it's not part of your wallet and you mistyped it, or you were a victim of a phishing (if you bought from third party seller)

I bought it directly from Ledger.

If you have 24 seed words than you should update to latest firmware because of security vulnerabilities which have been found.Maybe with new firmware your problem can be solved,but I doubt this because of what you wrote.

Yes, it's not a firmware problem.

If address is not show under option "Sign Message", then it is not part of your wallet,and this we can conclude by the fact that you admit you never copy/paste that address which is usual and safe way to do that.You take that address in a photo,and then you typed it manually in the wallet from which you sent BTC to Ledger Nano S.

The BTC Segwit Address definitely came from my Ledger Nano S. It is impossible to make up an address, also the transaction is confirmed ob Blockchain. Copy and pasting the address is not the safest option.

If this is not a problem with wallet sync or outdated firmware,then problem is that you typed that SegWit address incorrectly.

The address was definitely typed correctly.

Please answer the following quetsions (to make it easier for us to help you):

• What versions are you using: Nano s firmware, bitcoin chrome application, bitcoin application (on the nano s)?
  
  I'm using firmware 1.3.1 - I have not updated my Ledger yet in fear of losing anything. I'm also using the standard Chrome Apps.
  
  
• Did you verify the receiving address on your nano s when clicking 'receive' in the bitcoin chrome app?
  
  Yes
  
  
• Does the address show up under 'Options' -> 'Tools' -> 'Sign message' from the drop-down menu?
  
  No
  
  
• Did you verify wether the copied(?) address from the receive-tab matched the address when pasted (to eliminate clipping malware)?
  
  I never copied or pasted the address, I took a photo of it and copied it correctly (checking 5 times before sending)
  
  
• Is this the 'first' time you are using your nano s? Did it work (without a flaw) previously?
  
  It worked fine when others were transferred on the same day (I also transferred BCH & LTC which were received ok).