You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
The text was updated successfully, but these errors were encountered:
We should change this, but it (of course) must be backward compatible with the current seed phrases.
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
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).
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)
The text was updated successfully, but these errors were encountered: