Bitcoin Forum
September 26, 2018, 04:02:00 PM *
News: ♦♦ New info! Bitcoin Core users absolutely must upgrade to previously-announced 0.16.3 [Torrent]. All Bitcoin users should temporarily trust confirmations slightly less. More info.
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Derive private key using BIP39 from Trezor's 24 seed  (Read 123 times)
pal4doom
Newbie
*
Offline Offline

Activity: 6
Merit: 0


View Profile
February 21, 2018, 03:03:39 AM
 #1

Hi Folks,

I'm trying to derive my private key for LTC/ETH from Trezor with 24 seed using the BIP39 https://iancoleman.io/bip39/


I'm lost as I can not find the right private key for the right Address that holds the funds.

Please can anyone help?

1537977720
Hero Member
*
Offline Offline

Posts: 1537977720

View Profile Personal Message (Offline)

Ignore
1537977720
Reply with quote  #2

1537977720
Report to moderator
1537977720
Hero Member
*
Offline Offline

Posts: 1537977720

View Profile Personal Message (Offline)

Ignore
1537977720
Reply with quote  #2

1537977720
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1537977720
Hero Member
*
Offline Offline

Posts: 1537977720

View Profile Personal Message (Offline)

Ignore
1537977720
Reply with quote  #2

1537977720
Report to moderator
1537977720
Hero Member
*
Offline Offline

Posts: 1537977720

View Profile Personal Message (Offline)

Ignore
1537977720
Reply with quote  #2

1537977720
Report to moderator
Xynerise
Sr. Member
****
Offline Offline

Activity: 280
Merit: 280

39twH4PSYgDSzU7sLnRoDfthR6gWYrrPoD


View Profile
February 21, 2018, 05:58:45 AM
 #2

Are you sure the seed is correct, that there are no misspellings?
Are the words in the correct order?
Are you using the correct derivation path?
IIRC Trezor's derivation path for ETH is m/44'/60'/0'/0/i
pal4doom
Newbie
*
Offline Offline

Activity: 6
Merit: 0


View Profile
February 21, 2018, 01:12:10 PM
 #3

Are you sure the seed is correct, that there are no misspellings?
Are the words in the correct order?
Are you using the correct derivation path?
IIRC Trezor's derivation path for ETH is m/44'/60'/0'/0/i

Thanks for your answer, Yes all is correct, the funny thing is that I can generate all the new addresses with their associated private keys using the BIP39, the same ones i see when i connect my Trezor on myetherwallet.

the only thing i can think of is the derivation path, because before when i was connecting my Trezor i was always selecting a derivation path for Trezor but do not remember what was it, it was just made for Trezor(ETH).

now it's mixed with Jax/Meta under the path m/44'/60'/0'/0/

I'm not sure what to do
pal4doom
Newbie
*
Offline Offline

Activity: 6
Merit: 0


View Profile
February 21, 2018, 01:32:07 PM
 #4

Is there a way to find the derivation path using my ETH address?
Xynerise
Sr. Member
****
Offline Offline

Activity: 280
Merit: 280

39twH4PSYgDSzU7sLnRoDfthR6gWYrrPoD


View Profile
February 21, 2018, 01:40:09 PM
 #5

Is there a way to find the derivation path using my ETH address?
I told you before above:

IIRC Trezor's derivation path for ETH is m/44'/60'/0'/0/
Trezor, Jaxx, Metamask, imtoken, and Exodus all use the same derivation path.

Quote
the funny thing is that I can generate all the new addresses with their associated private keys using the BIP39, the same ones i see when i connect my Trezor on myetherwallet.
Huh
What then is the problem? Huh
If you generate the same addresses that means you're using the right seed and path.
pal4doom
Newbie
*
Offline Offline

Activity: 6
Merit: 0


View Profile
February 21, 2018, 02:41:22 PM
 #6

Is there a way to find the derivation path using my ETH address?
I told you before above:

IIRC Trezor's derivation path for ETH is m/44'/60'/0'/0/
Trezor, Jaxx, Metamask, imtoken, and Exodus all use the same derivation path.

Quote
the funny thing is that I can generate all the new addresses with their associated private keys using the BIP39, the same ones i see when i connect my Trezor on myetherwallet.
Huh
What then is the problem? Huh
If you generate the same addresses that means you're using the right seed and path.


Thanks a lot, I fixed it, I was using a different derivation path which was not the Trezor's default one. Thanks a lot for your help.

Another thing i am unsure about is deriving my LTC private key for my Segwit addresses that start with M on my trezor.

m/49'/2'/0'/0    --> this one is for M Segwit LTC
m/44'/2'/0'/0    ---> this one is for Legacy LTC

when I derive their private keys, they both come as Lxxxxxxxxx and it's not a match for the M addresses for Segwit in my trezor.

I'm totally lost in this one as I'm not even sure if its possible to derive private key for M segwit address and import it into LTC core

Thanks!




icberg1
Newbie
*
Offline Offline

Activity: 13
Merit: 0


View Profile
February 21, 2018, 03:16:51 PM
 #7

Hi Gents,

i'm having similar issue with deriving the private keys from the seed provided by Blockchain.info web wallet; Iancoleman tool gave me all the privkeys except for the address that held my bitcoin in time of hard-forks. I already contacted the the support team of blockchain.info but no answer
Please advise 
Thanks in advance
Xynerise
Sr. Member
****
Offline Offline

Activity: 280
Merit: 280

39twH4PSYgDSzU7sLnRoDfthR6gWYrrPoD


View Profile
February 21, 2018, 04:47:44 PM
 #8



Thanks a lot, I fixed it, I was using a different derivation path which was not the Trezor's default one. Thanks a lot for your help.

Another thing i am unsure about is deriving my LTC private key for my Segwit addresses that start with M on my trezor.

m/49'/2'/0'/0    --> this one is for M Segwit LTC
m/44'/2'/0'/0    ---> this one is for Legacy LTC

when I derive their private keys, they both come as Lxxxxxxxxx and it's not a match for the M addresses for Segwit in my trezor.

I'm totally lost in this one as I'm not even sure if its possible to derive private key for M segwit address and import it into LTC core

Thanks!

m/49'/2'/0'/0/0 is the Segwit LTC derivation path.
Are you sure you're using the 49 Tab on Ian Coleman's tool?
Xynerise
Sr. Member
****
Offline Offline

Activity: 280
Merit: 280

39twH4PSYgDSzU7sLnRoDfthR6gWYrrPoD


View Profile
February 21, 2018, 05:30:28 PM
 #9

Hi Gents,

i'm having similar issue with deriving the private keys from the seed provided by Blockchain.info web wallet; Iancoleman tool gave me all the privkeys except for the address that held my bitcoin in time of hard-forks. I already contacted the the support team of blockchain.info but no answer
Please advise 
Thanks in advance
Did you use the correct derivation path?
Blockchain.info uses  m/44'/0'/0'
Check the list for your address, or send the bitcoin into another wallet and import the seed into a compatible fork wallet.
pal4doom
Newbie
*
Offline Offline

Activity: 6
Merit: 0


View Profile
February 22, 2018, 01:10:28 AM
 #10



Thanks a lot, I fixed it, I was using a different derivation path which was not the Trezor's default one. Thanks a lot for your help.

Another thing i am unsure about is deriving my LTC private key for my Segwit addresses that start with M on my trezor.

m/49'/2'/0'/0    --> this one is for M Segwit LTC
m/44'/2'/0'/0    ---> this one is for Legacy LTC

when I derive their private keys, they both come as Lxxxxxxxxx and it's not a match for the M addresses for Segwit in my trezor.

I'm totally lost in this one as I'm not even sure if its possible to derive private key for M segwit address and import it into LTC core

Thanks!

m/49'/2'/0'/0/0 is the Segwit LTC derivation path.
Are you sure you're using the 49 Tab on Ian Coleman's tool?

Hi mate!

Thanks for your help and replies, really good.

the path is m/49'/2'/0'/0 --Yes.

the problem was - I needed to import all LTC private keys that were in my trezor's wallet. and then I needed to addwintess address from debug console as many as the number of imported private keys.


Xynerise
Sr. Member
****
Offline Offline

Activity: 280
Merit: 280

39twH4PSYgDSzU7sLnRoDfthR6gWYrrPoD


View Profile
February 22, 2018, 05:16:01 AM
 #11

Hi mate!

Thanks for your help and replies, really good.

the path is m/49'/2'/0'/0 --Yes.

the problem was - I needed to import all LTC private keys that were in my trezor's wallet. and then I needed to addwintess address from debug console as many as the number of imported private keys.

So your problem was in importing the private keys into LTC Core and not in generating the private key with Ian Coleman's tool.
Glad you have everything sorted out now.
HCP
Hero Member
*****
Offline Offline

Activity: 728
Merit: 925

<insert witty quote here>


View Profile
February 22, 2018, 05:47:36 AM
 #12

i'm having similar issue with deriving the private keys from the seed provided by Blockchain.info web wallet; Iancoleman tool gave me all the privkeys except for the address that held my bitcoin in time of hard-forks. I already contacted the the support team of blockchain.info but no answer
Two things that might be worth checking:

1. If you imported a private key into your blockchain.info wallet, and your funds were on that private key/address, you won't be able to get the private key using the Mnemonic Code Converter (aka "Ian Coleman tool") and your b.info seed mnemonic. You should however be able to export it manually from within b.info wallet. (Settings -> Addressed -> Imported Bitcoin Addresses)

2. It has been a while, so I don't remember if b.info uses "change" addresses or not. I think they do. So, you may need to change the derivation path slightly to find the address that has your coins...

On the Mnemonic Code Converter, enter your seed mnemonic in the "BIP39 Mnemonic" box and then click the "BIP44" tab. You should see your "receive" addresses and private keys displayed at the bottom... now change the "External/Internal" value from 0 to 1. Now you should see your "change" addresses and associated private keys displayed a the bottom.

Hopefully, your "missing" address is here! Wink




Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!