Skip to content
This repository has been archived by the owner on Apr 17, 2023. It is now read-only.

On restore, blockstack IDs show up as incomplete until first refresh #1009

Closed
larrysalibra opened this issue Nov 1, 2017 · 3 comments
Closed

Comments

@larrysalibra
Copy link
Collaborator

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)

@larrysalibra 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
@john-light
Copy link

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.

@larrysalibra
Copy link
Collaborator Author

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

@wbobeirne
Copy link
Contributor

The original issue has been resolved by #1576. The other issue mentioned is tracked in #1550 now.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants