Pages:
Author

Topic: BTC Segwit Address not recognised by my Ledger Nano S Wallet (Read 802 times)

legendary
Activity: 1624
Merit: 2481
do you think this would also be the case for RDH40's problem? did he ever say anything about pairing Ledger+Electrum?
his seed mnemonic might have been generated by electrum, which might also be a valid BIP39 Mnemonic phrase
so when he tried it on iancoleman's page it gives out the BIP39 version instead of Electrum version

Thats probably not the case.
OP mentioned the address has been generated by his ledger.

Regardless of whether you use the nano s with the chrome application or electrum, the device will still generate the seed/private keys itself.
Electrum is just a UI to access the nano s. Therefore the seed/keys generated by the nano s are always BIP39, regardless of which software is used to access the wallet.
hero member
Activity: 1232
Merit: 738
Mixing reinvented for your privacy | chipmixer.com
One of the key differences is that the BIP39 spec (and by extension IanColeman tool) uses a passphrase of "mnemonic" + yourpassphrase... whereas Electrum uses a passphrase of "electrum" + yourpassphrase.
thanks for the hint! I just need to modify 2 lines and it works with electrum "seed mnemonic" Wink

do you think this would also be the case for RDH40's problem? did he ever say anything about pairing Ledger+Electrum?
his seed mnemonic might have been generated by electrum, which might also be a valid BIP39 Mnemonic phrase
so when he tried it on iancoleman's page it gives out the BIP39 version instead of Electrum version
HCP
legendary
Activity: 2086
Merit: 4361
I was trying some Electrum seeds from bitcoin quest on iancoleman BIP39 page but the page keeps saying invalid mnemonic
This doesn't surprise me due to Electrum generating/converting mnemonics in a different way from BIP39. You can actually edit the IanColeman source code and get it to spit out the Electrum addresses from an Electrum mnemonic... I did it on an older version of the code, but I assume it won't have changed too much.

One of the key differences is that the BIP39 spec (and by extension IanColeman tool) uses a passphrase of "mnemonic" + yourpassphrase... whereas Electrum uses a passphrase of "electrum" + yourpassphrase.

Quote
I was thinking maybe the same seed works on BIP39 and Electrum might actually derives different addresses if it was generated by Electrum
So, yes... the same seed mnemonic (ie. "12 words") will definitely generate different addresses, as that mnemonic will actually be converted to differents seeds (ie. the actual number) by Ian Coleman Tool and Electrum.

This is why I always try to explicitly highlight the difference between a "seed" (actual number)... and a "seed mnemonic" (words).
hero member
Activity: 1232
Merit: 738
Mixing reinvented for your privacy | chipmixer.com
Another interesting point is that the seed mnemonic davedee has is actually recognised as a "SegWit" seed by Electrum... Even though it is supposedly a BIP39 seed generated by a Trezor??!?

This leads me to believe that, at least in davedee's case,  the seed they have written down is actually an Electrum seed... and not the actual seed from their Trezor that generated the "3". Undecided

To think about it, has he ever tried it directly on Electrum (BTC)? @RDH40 please try it on Electrum
I was trying some Electrum seeds from bitcoin quest on iancoleman BIP39 page but the page keeps saying invalid mnemonic
I was thinking maybe the same seed works on BIP39 and Electrum might actually derives different addresses if it was generated by Electrum
HCP
legendary
Activity: 2086
Merit: 4361
Don't give up, exhaust all possibilities. Did you follow the steps i told you to do?
Just so you know...

I attempted your solution with Electrum-LTC on behalf of davedee to rule out a similar issue... However, the LTC "M" address matching the "3" address that davedee sent BTC funds to (found using this converter https://litecoin-project.github.io/p2sh-convert/), does not appear in the list of addresses generated in Electrum-LTC...

Another interesting point is that the seed mnemonic davedee has is actually recognised as a "SegWit" seed by Electrum... Even though it is supposedly a BIP39 seed generated by a Trezor??!?

This leads me to believe that, at least in davedee's case,  the seed they have written down is actually an Electrum seed... and not the actual seed from their Trezor that generated the "3". Undecided

jr. member
Activity: 33
Merit: 1
Don't give up, exhaust all possibilities. Did you follow the steps i told you to do?
jr. member
Activity: 38
Merit: 4
@RHD40, i am still waiting for our reply Smiley, did you do exactly what i said? you should have recovered the coins by now, if not you can shoot me a PM.

Hello,

I have tried literally everything but I am so frustrated that I have almost given up. Can not understand how my Ledger Nano S can now not recognise my BTC Segwit address where my coins are!
jr. member
Activity: 33
Merit: 1
@RHD40, i am still waiting for our reply Smiley, did you do exactly what i said? you should have recovered the coins by now, if not you can shoot me a PM.
newbie
Activity: 18
Merit: 0
i have tried walletrecoveryservices and he couldn't solve it, so i guess i have nothing to loose.
legendary
Activity: 1624
Merit: 2481
Unfortunately no, and at this point I'm willing to give out my seed to anyone if they promise to send half back if they can recover the coins. I feel it's better than letting the coins sit there.

This is a bad idea. You might once find out what happend. Maybe something trivial.  
If you post it publicly here the chances are high you won't get anything (if it can be recovered at all).

Did you start a thread here with useful information regarding your problem? Mind giving me the link?
sr. member
Activity: 322
Merit: 363
39twH4PSYgDSzU7sLnRoDfthR6gWYrrPoD
Unfortunately no, and at this point I'm willing to give out my seed to anyone if they promise to send half back if they can recover the coins. I feel it's better than letting the coins sit there.
Not a good idea at all.
There's no guarantee that you'd ever get the coins if they manage to access it but IF you're going to toe that line then Dave of Wallet Recovery Services is generally trustworthy although his speciality seems to be in forgotten passwords for wallet.dat files.
newbie
Activity: 18
Merit: 0
Unfortunately no, and at this point I'm willing to give out my seed to anyone if they promise to send half back if they can recover the coins. I feel it's better than letting the coins sit there.
sr. member
Activity: 322
Merit: 363
39twH4PSYgDSzU7sLnRoDfthR6gWYrrPoD
Hi, you still have this problem?
What about you?
I remember you opened a similar thread.
Is it solved now?
newbie
Activity: 18
Merit: 0
Hi, you still have this problem?
jr. member
Activity: 33
Merit: 1
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


Hi,

I tried this and it only shows my LTC transactions, nothing else. Also there is no option to 'go to the address tab' and look for any addresses.


Open electrum ltc, click on view and click show addresses, the address tab should pop up.
jr. member
Activity: 38
Merit: 4
Is there a way on your ledger to turn on/off segwit address usage?
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... ? ? ? Huh

It seems I'm doomed! Think we've run out of all possibilities!
jr. member
Activity: 38
Merit: 4
Its obvious you can't help me
Then maybe tell us what you've already tried unsuccessfully? If you've already spent months with Ledger support, you probably should have led with that in the OP...
@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

I did a ledger reset before I sent the 2 addresses to my friend but I don't think this is the problem as my LTC arrived fine.
No, I reset the ledger as I thought it wasn't working properly or I had set it up wrong. It gave me a new 24 word seed. Then I obtained both the BTC & LTC addresses separately - both SegWit. When I check my accounts on the ledger I always select the SegWit options as these were the addresses I obtained. When I got the addresses I got them from the 'Receive' option, not the 'Sign message' option in settings-tools.
Do you think my ledger could be damaged?
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
jr. member
Activity: 38
Merit: 4
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


Hi,

I tried this and it only shows my LTC transactions, nothing else. Also there is no option to 'go to the address tab' and look for any addresses.
HCP
legendary
Activity: 2086
Merit: 4361
Is there a way on your ledger to turn on/off segwit address usage?
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.

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.

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... ? ? ? Huh
hero member
Activity: 1232
Merit: 738
Mixing reinvented for your privacy | chipmixer.com
Hi, i know what your problem is and i will post the guide here on how to recover the coins, if you agree to leave a tip after you've claimed it?
did you just create a new bitcointalk account for posting reply in this thread? Huh

---snip---
It seems that the ledger does not recognise the BTC Segwit Address it gave me for whatever reason.
---snip---
Since then I have learnt that the ledgers xpub does not match the BTC Segwit Address but it does the BCH & LTC - so how is this possible?
Is there a way on your ledger to turn on/off segwit address usage?

HCP has told you how to use iancoleman tool by using xpub in the old thread post #8
but please try again this time with the 24 word seed you have
- paste your 24 word seed into "BIP39 Mnemonic" input text, and make sure BTC is selected
- on "Derivation Path", click "BIP49" and check the addresses
- try a few times with alternate combinations "Account" 0 or 1 and "External/Internal" 0 or 1
- if with all 4 combinations you still cannot find the address, try BIP141
- go back to "Derivation Path" and click "BIP141", make sure "Script Semantics" is P2WPKH nested in P2SH
- try different "BIP32 Derivation Path" (above "Script Semantics") with m/0 and m/1
- if you still cannot find the address, keep fiddling this tool with any possible derivation path you can think of
your address must be generated somehow from the seed with certain derivation path
Pages:
Jump to: