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
Comments
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 |
Tested 5 times now with my seed generated from Umbrel. It dosent say that
the seed is invalid, just get returned to the menu.
Same happened with the seed from Blixt wallet.
Den fre 28 jan. 2022 kl 00:43 skrev asvdf ***@***.***>:
… 90% 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 wouldn't work on SS
—
Reply to this email directly, view it on GitHub
<#137 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AE7PN3GNORHE2NQ5DI6LKYDUYHKBVANCNFSM5MDFFWMQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Wouldn't know about Blixt, but Umbrel lightning node uses lnd, which in turn uses aezeed, which is not BIP39 compatible |
Now I understand, thanks for the info.
…On Fri, 28 Jan 2022, 15:15 asvdf, ***@***.***> wrote:
Wouldn't know about Blixt, but Umbrel lightning node uses lnd, which in
turn uses aezeed, which is not BIP39 compatible
—
Reply to this email directly, view it on GitHub
<#137 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AE7PN3HO64R3FVFFQ23X373UYKQJ5ANCNFSM5MDFFWMQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
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. |
Great, thanks for the info, great support and amazing product.
…On Fri, 28 Jan 2022, 17:32 SeedSigner, ***@***.***> wrote:
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.
—
Reply to this email directly, view it on GitHub
<#137 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AE7PN3FOHIV5FMAJDGWHASDUYLAKNANCNFSM5MDFFWMQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
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. |
Thank you for looking into it on their end as well. |
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. |
Done
Den sön 1 maj 2022 kl 16:30 skrev kdmukai ***@***.***>:
… 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 <https://github.com/newtonick> you can close this issue.
—
Reply to this email directly, view it on GitHub
<#137 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AE7PN3B2AP7Q7US23T6YCELVH2IPLANCNFSM5MDFFWMQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
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
The text was updated successfully, but these errors were encountered: