-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Seed phrase should be forced to lowercase before test/importing #8171
Comments
Whitespace other than space characters should also either be stripped or replaced with spaces, which can then be limited to 1 space between each word as part of the sanitation. |
The user-specified seed phrase during the first-time-flow import step required the phrase to be entered in all lowercase. The case does not add any extra entropy to the seed, so there's no reason to be case sensitive. Flexibility here will improve the onboarding UX. This commit makes the entered seed phrase case insensitive. Fixes MetaMask#8171
The user-specified seed phrase during the first-time-flow import step required the phrase to be entered in all lowercase. The case does not add any extra entropy to the seed, so there's no reason to be case sensitive. Flexibility here will improve the onboarding UX. This commit makes the entered seed phrase case-insensitive. Fixes #8171
This is fixed with #8246, and will be in our next release. Thanks for bringing this up!
This should already work as expected, I can import seed phrases with newlines and tab characters and multiple spaces. Feel free to open up another issue if this isn't the case for you. |
When importing a seed phrase recorded in upper-case for legibility it is rejected as invalid.
Expected behavior
Valid seed phrases should import correctly. Rejecting valid seeds as being "invalid" because of their case only functions to raise user's blood pressure and cause time wasted seeking answers.
The text was updated successfully, but these errors were encountered: