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

Passphrase support #47

Open
rc-fire opened this issue Feb 8, 2022 · 1 comment
Open

Passphrase support #47

rc-fire opened this issue Feb 8, 2022 · 1 comment

Comments

@rc-fire
Copy link

rc-fire commented Feb 8, 2022

Is there any way to use this tool for recovery (2 of 2) if the wallet used a passphrase (as supported by jade wallet since 2021-10-20) with a 12 or 24 word seed?

I don't see a passphrase anywhere mentioned in the docs or source, and the last update was 5 moths ago.

By the mess you made with the passphrase implementation on the jade hardware wallet there will soon be a lot of people needing to recover their passphrases systematically. As explanation: The wallet only requires you to type the passphrase once, this leaves room for typos. Other wallets (like Trezor) especially let you enter the passphrase 2 times - and if they detect an unused wallet give you a warning and even want a third entry of the passphrase.

@JamieDriver
Copy link
Contributor

The tool does accept seed hex (suffixed with an 'X' - in place of mnemonic), so if you were using eg. a trezor and were using passphrase, this is how you'd do the recovery. (ie. derive the seed from mnemonic + passphrase externally, and pass the seed as hex into the tool).

However - your point is fair, especially since Jade supports passphrase, so I have added the option to pass any passphrase in, similar to mnemonic (ie. via a file, or via console entry).

If you want to discuss the details of passphrase entry on the Jade hw, please raise an issue in the Jade repo.

Many thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants