-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Allow user to define derivation path #7486
Labels
Comments
Custom derivation path option for imported hardware wallets is very much needed! |
Related to #8698 as well |
The ultimate feature would be to brute force the ethereum address when connecting the HD wallet. |
I second this as a valid issue and having this feature would dramatically help me out when using Metamask |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What problem are you trying to solve?
It seems there are a few cases where people would like to use derivation paths not currently supported by MetaMask.
m/44'/60'/0'/0
for Ledger wallets. #671644'/1'/0'/0
for my Rinkeby accounts since this is also what Frame uses for Rinkeby accounts.Describe the solution you'd like
I think rather than adding every possible derivation path users could want as a pre-set, MetaMask could simply give users the ability to set their own derivation path when setting up the wallet, for software and hardware wallets alike.
The text was updated successfully, but these errors were encountered: