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 Apr 17, 2023. It is now read-only.
We should have some sort of "loading" indicator or message until the first run of "refreshIdentities" completes and the browser determines whether or not the address owns a name, has a profile and has verified identities.
This should happen on both account restore and creating a new blockstack id (because they could potentially already have profiles/names)
The text was updated successfully, but these errors were encountered:
larrysalibra
changed the title
On restore, blockstack IDs show up as uncompleted until first refresh
On restore, blockstack IDs show up as incomplete until first refresh
Nov 1, 2017
Does "refreshIdentities" automatically cycle through the keychain to see if any of the addresses own IDs? Right now I have to manually "brute force" and create new IDs in order to find additional IDs my keychain owns each time I open the browser.
Does "refreshIdentities" automatically cycle through the keychain to see if any of the addresses own IDs? Right now I have to manually "brute force" and create new IDs in order to find additional IDs my keychain owns each time I open the browser.
No, it doesn't. This is something we need to implement in the restore process. We don't store the keychain phrase (master secret) in plaintext, so to implement this is refreshIdentities, we'd have to prompt users for their password to decrypt the secret each time.
Here's the issue for improving the restore process: #729
We should have some sort of "loading" indicator or message until the first run of "refreshIdentities" completes and the browser determines whether or not the address owns a name, has a profile and has verified identities.
This should happen on both account restore and creating a new blockstack id (because they could potentially already have profiles/names)
The text was updated successfully, but these errors were encountered: