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

Manually enter 24 word seed not saved #137

Closed
jessjamesjones opened this issue Jan 16, 2022 · 10 comments
Closed

Manually enter 24 word seed not saved #137

jessjamesjones opened this issue Jan 16, 2022 · 10 comments

Comments

@jessjamesjones
Copy link

When I manually enter 24 word seed in "Temp Seed Storage", the seed is not saved, instead I get returned to "Temp Seed Storage" page

@GordianLN
Copy link

GordianLN commented Jan 27, 2022

99% chance it's because the last word is not a valid checksum, are you sure you entered it 100% correct, and it is a BIP39 compliant seed? For example aezeed, used by lnd, wouldn't work on SS

@jessjamesjones
Copy link
Author

jessjamesjones commented Jan 28, 2022 via email

@GordianLN
Copy link

Wouldn't know about Blixt, but Umbrel lightning node uses lnd, which in turn uses aezeed, which is not BIP39 compatible

@jessjamesjones
Copy link
Author

jessjamesjones commented Jan 28, 2022 via email

@SeedSigner
Copy link
Owner

I have also recently encountered this issue when entering a seed that was generated with Electrum, which is also not BIP39 compatible. While we may not support alternate seed implementations any time soon, we can do better with the messaging when this issue arises, so I am going to leave this issue open as a reminder.

@jessjamesjones
Copy link
Author

jessjamesjones commented Jan 28, 2022 via email

@justo4
Copy link

justo4 commented Feb 11, 2022

I've had the same problem. I'll look on the getumbrel git to see if it's been made an issue vis-a-vis BIP39 legit seeds. Thanks for keeping this active.

@SeedSigner
Copy link
Owner

Thank you for looking into it on their end as well.

@kdmukai
Copy link
Contributor

kdmukai commented May 1, 2022

v0.5.0 now has an "Invalid Mnemonic!" warning screen that lets you either go back and edit your seed phrase or discard it.

@newtonick you can close this issue.

@jessjamesjones
Copy link
Author

jessjamesjones commented May 2, 2022 via email

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

5 participants