-
Notifications
You must be signed in to change notification settings - Fork 35
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
Custom BIP44 derivation paths #894
Comments
Hi @lbeder , thanks for this suggestion. We got this idea very long ago (from the project start) and we found this functionality was quite advanced for all users. We'd like to collect more user feedback on this and determine when and how we can implement this. |
It is indeed dangerous, will need to warn and educate user. There is use case it is mandatory to change derivation path, for example subaccounts from trezor and ledger. Without being able to change path, we can only access account 0 of trezor and ledger.... |
Hi @soralit, Being able to use multiple paths is very useful to manage wallets that have lots of addresses in them. For example, instead of having only 1 path with 500 accounts in it, the user can make multiple paths for different use cases.
I understand the average user may not have many accounts, so they might not need this function. But it would definitely be a useful option. It could even be something only enabled in "expert mode" settings if you felt that would be more appropriate. |
This is such a dealbreaker since people like to store crypto for their family and friends. No one wants to mix coins in 1 account and that is why Ledger gives us option to create multiple accounts. Multiple accounts are just different derivation path: For Taproot: Currently, Keystone is not supporting it and it's such a bummer. Because of this, we cannot even sign transactions for different accounts and the coins are just stuck there unless we get a ledger. |
I totally agree with @niveshsaharan. My assumption was that this is a basic feature of all hardware wallets. Now I also have to stick with Ledger which I wanted to get rid of. @keystoneGithub what are the major problems with implementing this feature? The "expert mode" switch suggested by @lbeder sounds nice. Experts may not be shocked to have more information packed on the screen. |
This is a hugely important feature for security and usability please add it |
Hi,
Are there any plans to support custom BIP44 derivation paths? Keystone is an awesome device, but it's currently impossible to use it with custom derivation paths.
Basiclly, I'd like to input an arbitrarily long string, i.e. m/44'/x'/y'/z'/....'/0 , and have the addresses generated from the path.
The text was updated successfully, but these errors were encountered: