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
Currently in Freighter, we ask for a user's password at the beginning of a session because all we store in localStorage is the user's encrypted key blobs. The password is needed to get both the public and private keys. The private key is erased after the session times out. The public key is erased when the user is upgraded/reloads the extension
We want to move to a UX where the password is only required when signing a tx (.i.e, when we need the private key). In order to accomplish this we will need to:
Acceptance Criteria:
Store all the user's public keys in localStorage so they persist after extension upgrade
Companion ticket:
Create password prompts when the user is about to sign a tx, but the private key is not available (this already exists for send/swap and sign tx/auth entry/message, but not change trustline). This can be handled in Adding an asset should feel like making a transaction #1671
The text was updated successfully, but these errors were encountered:
piyalbasu
changed the title
Only ask for user password when signing tx's
Don't ask for password on app start up if we the user has already created an account
Jan 21, 2025
Currently in Freighter, we ask for a user's password at the beginning of a session because all we store in localStorage is the user's encrypted key blobs. The password is needed to get both the public and private keys. The private key is erased after the session times out. The public key is erased when the user is upgraded/reloads the extension
We want to move to a UX where the password is only required when signing a tx (.i.e, when we need the private key). In order to accomplish this we will need to:
Acceptance Criteria:
Companion ticket:
The text was updated successfully, but these errors were encountered: