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

Importing an existing wallet should help with mnemonic phrase validation #135

Open
sbrekelmans opened this issue Jan 13, 2021 · 3 comments

Comments

@sbrekelmans
Copy link
Contributor

In the tech support chat, we get a lot of wallet import questions that relate to typos, casing, spaces, trailing or otherwise. It would help a great deal if importing an existing seed would have a BIP39 validation, that would give a warning to the user before opening the corresponding wallet/address.

When a user imports a wallet that doesn't conform to BIP39 standard, a warning could be given to allow the user the possibility to check for errors before continuing. ("import is not a valid bip39 phrase, continue anyway?" for example)

@jasny
Copy link
Member

jasny commented Jan 14, 2021

The LTO Seed phrase isn't compatible with BIP39. It's an unfortunate side effect of forking Waves.
https://medium.com/wavesprotocol/hd-wallet-creation-with-waves-39371d29d7bd

We should change this, but it (of course) must be backward compatible with the current seed phrases.

@jasny jasny changed the title Importing an existing wallet should help with BIP39 validation Importing an existing wallet should help with mnemonic phrase validation Jan 14, 2021
@sbrekelmans
Copy link
Contributor Author

sbrekelmans commented Jan 15, 2021

Fine, the end goal is to help users by warning about preventable mistakes. I think we could verify and warn when a user tries to import (among others):

  • seed words with capital letters
  • phrases with leading or trailing spaces
  • more than1 space in between words
  • words not on the word list
  • non-default word seed phrase length (so any other amount than 15 words)

All these issues change the phrase I believe (ie result in a different address).

@justmvg
Copy link
Contributor

justmvg commented Jun 13, 2021

Enhancements on importing an existing seed have been pushed with PR #156

Would that be sufficient enough to close this issue?

@sbrekelmans @jasny

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

3 participants