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
{{ message }}
This repository has been archived by the owner on Mar 28, 2023. It is now read-only.
DB encryption is not the same as password protecting the seed from being read on the client.
@hoffmabc@jjeffryes Given the client has free access to the seed string during runtime, what server requirements do you believe there are here? How would this interaction work? Priority?
I think this is kind of what we were discussing on the web version about encrypting the seed phrase with a password like MetaMask does. The client would require a password client side and the server would just return the encrypted seed phrase. The password would decrypt it client side to show the user.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Self-explanatory as to feature. Would be nice to be able to optionally protect seed viewing with a password in the client.
The text was updated successfully, but these errors were encountered: