Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add custom HD derivation path option for Trezor #11197

Open
rdymac opened this issue May 27, 2021 · 1 comment
Open

Add custom HD derivation path option for Trezor #11197

rdymac opened this issue May 27, 2021 · 1 comment

Comments

@rdymac
Copy link

rdymac commented May 27, 2021

The custom derivation path was merged for Ledger #9367 (it is not yet available as of version 9.5.4, though).

Something similar might be needed for Trezor's integration too:

@vondra: I moved from Ledger to Trezor. I need to connect to m/44'/60'/0' addresses. When I connect Trezor is there a option how to manualy set derivation path or invoke the path selector ?

Comment

This support article will need to be updated once the Custom Derivation Path is available for either Ledger or Trezor.

@TbLtzk
Copy link

TbLtzk commented Jul 26, 2024

Any activity here? I am currently using a Ledger Nano S with Ledger Live HD path:
m/44'/60'/<account>'/0/0

Now I'm trying to use a trezor with the same seed phrase. But when reading the accounts I see only those options:

image

It treats Ledger and MEW together as legacy, which is not correct. From #9367 we see that we have

  • Ledger Live: m/44'/60'/0'/0/0
  • Legacy (MEW / MyCrypto): m/44'/60'/0'

The first account on Trezor is the same as on Ledger Live: m/44'/60'/0'/0/0, but afterwards it diverges:

  • Ledger Live: m/44'/60'/1'/0/0
  • Trezor: m/44'/60'/0'/0/1

So I have no chance to import my Ledger Live accounts via Trezor to MetaMask except the very first one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment