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
Manually add new public keys to existing device #696
Comments
Anyone else trying to do the same: for now, it seems you can change the Device Type to 'Other' and you can do this. Then switch back. |
Yes, we did it on purpose because people were making mistakes - pasting xpubs without derivations or with a wrong derivation, using them for a wrong purpose etc. |
I'm not sure i understand the value of that "feature". Would you be fine with closing that as "won't fix"? |
This should be an option, even if advanced or more hidden. But that workaround of changing to other and back is not the correct solution. And we definitely need this as an option for all user types. Trying to add custom wallets from Unchained Capital for example that uses a custom m/45/0/0/0 derivation path is not possible since most hardware wallets don't add that one even if you plug them in. |
Thanks for that explanation Ben, I got to say that's not intuitive at all in the UI, I was looking for a way to enter the XPUB manually myself on that screen. Didn't know I'll have to go through USB/File instead, can we have an advanced option to enter all these manually including the XPUB? For some of the wallets, I need to enter it for 3rd party providers that I don't have an HW. Thanks again! |
Hi, I think for the 3rd party providers, since you should add them as a separate device, you should choose "Other" as their device type. If you do that, then you'll have an option to paste an xpub which will get added to the list then. |
At the moment, if you want to add more keys to, say, a Trezor, the only option is to plug in the device. It would be nice to be able to manually add these just like you can when you manually create a new device.
The text was updated successfully, but these errors were encountered: