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 Ledger Ethereum Derivation Path #2448

Closed
Kryptoxic opened this issue Mar 22, 2019 · 2 comments
Closed

Add Ledger Ethereum Derivation Path #2448

Kryptoxic opened this issue Mar 22, 2019 · 2 comments
Labels
type: enhancement Items that improve overall user experience and/or expand on existing features.

Comments

@Kryptoxic
Copy link

If you're suggesting a feature, make sure someone hasn't already posted it. If
no one has, please provide the following information:

Description of the Feature

Ethereum addresses on Ledger Live makes use of a different derivation path (m/44'/60'). Currently the option named "Ledger ETH" on MyCrypto is using the legacy derivation path and not the Ledger Live derivation path.

Example(s) of Feature

A solution would be to do something similar to MEW and default the "Ledger ETH" option to the Ledger Live derivation path and rename the old one to "Legacy ETH".

image

The screenshot above shows an example from MEW that you guys can consider when adding the option.

I believe there is an issue open on this specific problem from the Ledger team themselves on issue #2070 but there has not been any replies since Nov 2018. I hope someone can give an update on this issue.

@tayvano
Copy link
Contributor

tayvano commented Mar 22, 2019

#2070 is going to be the place to track this. It's at the top of our backlog, it just takes quite a bit of effort. You can use the "custom path" for now and just know, we're well aware of how frustrating this is.

@tayvano tayvano added the type: enhancement Items that improve overall user experience and/or expand on existing features. label Apr 5, 2019
@wtzb
Copy link
Collaborator

wtzb commented Jan 27, 2020

Thanks for opening this issue! In an attempt to clean up our Github issues, I'm closing this and will mention #2070, which discusses this issue further.

We really appreciate you opening this issue and for your suggestion, I hope we can provide a solid solution in our beta soon!

@wtzb wtzb closed this as completed Jan 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement Items that improve overall user experience and/or expand on existing features.
Projects
None yet
Development

No branches or pull requests

3 participants